Apparatus, methods, and systems with a configurable spatial accelerator

ABSTRACT

Systems, methods, and apparatuses relating to a configurable spatial accelerator are described. In one embodiment, a processor includes a core with a decoder to decode an instruction into a decoded instruction and an execution unit to execute the decoded instruction to perform a first operation; a plurality of processing elements; and an interconnect network between the plurality of processing elements to receive an input of a dataflow graph comprising a plurality of nodes, wherein the dataflow graph is to be overlaid into the interconnect network and the plurality of processing elements with each node represented as a dataflow operator in the plurality of processing elements, and the plurality of processing elements are to perform a second operation by a respective, incoming operand set arriving at each of the dataflow operators of the plurality of processing elements.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH AND DEVELOPMENT

This invention was made with Government support under contract numberH98230A-13-D-0124/0001 awarded by the Department of Defense. TheGovernment has certain rights in this invention.

TECHNICAL FIELD

The disclosure relates generally to electronics, and, more specifically,an embodiment of the disclosure relates to a configurable spatialaccelerator.

BACKGROUND

A processor, or set of processors, executes instructions from aninstruction set, e.g., the instruction set architecture (ISA). Theinstruction set is the part of the computer architecture related toprogramming, and generally includes the native data types, instructions,register architecture, addressing modes, memory architecture, interruptand exception handling, and external input and output (I/O). It shouldbe noted that the term instruction herein may refer to amacro-instruction, e.g., an instruction that is provided to theprocessor for execution, or to a micro-instruction, e.g., an instructionthat results from a processor's decoder decoding macro-instructions.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is illustrated by way of example and notlimitation in the figures of the accompanying drawings, in which likereferences indicate similar elements and in which:

FIG. 1 illustrates an accelerator tile according to embodiments of thedisclosure.

FIG. 2 illustrates a hardware processor coupled to a memory according toembodiments of the disclosure.

FIG. 3A illustrates a program source according to embodiments of thedisclosure.

FIG. 3B illustrates a dataflow graph for the program source of FIG. 3Aaccording to embodiments of the disclosure.

FIG. 3C illustrates an accelerator with a plurality of processingelements configured to execute the dataflow graph of FIG. 3B accordingto embodiments of the disclosure.

FIG. 4 illustrates an example execution of a dataflow graph according toembodiments of the disclosure.

FIG. 5 illustrates a program source according to embodiments of thedisclosure.

FIG. 6 illustrates an accelerator tile comprising an array of processingelements according to embodiments of the disclosure.

FIG. 7A illustrates a configurable data path network according toembodiments of the disclosure.

FIG. 7B illustrates a configurable flow control path network accordingto embodiments of the disclosure.

FIG. 8 illustrates a hardware processor tile comprising an acceleratoraccording to embodiments of the disclosure.

FIG. 9 illustrates a processing element according to embodiments of thedisclosure.

FIG. 10 illustrates a request address file (RAF) circuit according toembodiments of the disclosure.

FIG. 11 illustrates a plurality of request address file (RAF) circuitscoupled between a plurality of accelerator tiles and a plurality ofcache banks according to embodiments of the disclosure.

FIG. 12 illustrates a data flow graph of a pseudocode function callaccording to embodiments of the disclosure.

FIG. 13 illustrates a spatial array of processing elements with aplurality of network dataflow endpoint circuits according to embodimentsof the disclosure.

FIG. 14 illustrates a network dataflow endpoint circuit according toembodiments of the disclosure.

FIG. 15 illustrates data formats for a send operation and a receiveoperation according to embodiments of the disclosure.

FIG. 16 illustrates another data format for a send operation accordingto embodiments of the disclosure.

FIG. 17 illustrates to configure a circuit element (e.g., networkdataflow endpoint circuit) data formats to configure a circuit element(e.g., network dataflow endpoint circuit) for a send (e.g., switch)operation and a receive (e.g., pick) operation according to embodimentsof the disclosure.

FIG. 18 illustrates a configuration data format to configure a circuitelement (e.g., network dataflow endpoint circuit) for a send operationwith its input, output, and control data annotated on a circuitaccording to embodiments of the disclosure.

FIG. 19 illustrates a configuration data format to configure a circuitelement (e.g., network dataflow endpoint circuit) for a selectedoperation with its input, output, and control data annotated on acircuit according to embodiments of the disclosure.

FIG. 20 illustrates a configuration data format to configure a circuitelement (e.g., network dataflow endpoint circuit) for a Switch operationwith its input, output, and control data annotated on a circuitaccording to embodiments of the disclosure.

FIG. 21 illustrates a configuration data format to configure a circuitelement (e.g., network dataflow endpoint circuit) for a SwitchAnyoperation with its input, output, and control data annotated on acircuit according to embodiments of the disclosure.

FIG. 22 illustrates a configuration data format to configure a circuitelement (e.g., network dataflow endpoint circuit) for a Pick operationwith its input, output, and control data annotated on a circuitaccording to embodiments of the disclosure.

FIG. 23 illustrates a configuration data format to configure a circuitelement (e.g., network dataflow endpoint circuit) for a PickAnyoperation with its input, output, and control data annotated on acircuit according to embodiments of the disclosure.

FIG. 24 illustrates selection of an operation by a network dataflowendpoint circuit for performance according to embodiments of thedisclosure.

FIG. 25 illustrates a network dataflow endpoint circuit according toembodiments of the disclosure.

FIG. 26 illustrates a network dataflow endpoint circuit receiving inputzero (0) while performing a pick operation according to embodiments ofthe disclosure.

FIG. 27 illustrates a network dataflow endpoint circuit receiving inputone (1) while performing a pick operation according to embodiments ofthe disclosure.

FIG. 28 illustrates a network dataflow endpoint circuit outputting theselected input while performing a pick operation according toembodiments of the disclosure.

FIG. 29 illustrates a flow diagram according to embodiments of thedisclosure.

FIG. 30 illustrates a system with a TLB manager circuit coupled to aplurality of request address file (RAF) circuits coupled between anaccelerator and a plurality of cache banks according to embodiments ofthe disclosure.

FIG. 31 illustrates a system with a plurality of request address file(RAF) circuits coupled between an accelerator and a plurality of cachebanks according to embodiments of the disclosure.

FIG. 32 illustrates a system with a plurality of request address file(RAF) circuits coupled between an accelerator and a plurality of cachebanks according to embodiments of the disclosure.

FIG. 33 illustrates a system with a plurality of accelerators accordingto embodiments of the disclosure.

FIG. 34 illustrates a flow diagram according to embodiments of thedisclosure.

FIG. 35 illustrates a system with a plurality of request address file(RAF) circuits coupled between an accelerator and a plurality of cachebanks according to embodiments of the disclosure.

FIG. 36 illustrates a system with a plurality of request address file(RAF) circuits coupled between an accelerator and a plurality of cachebanks according to embodiments of the disclosure.

FIG. 37 illustrates a flow diagram according to embodiments of thedisclosure.

FIG. 38 illustrates a request address file (RAF) circuit according toembodiments of the disclosure.

FIG. 39 illustrates a floating point multiplier partitioned into threeregions (the result region, three potential carry regions, and the gatedregion) according to embodiments of the disclosure.

FIG. 40 illustrates an in-flight configuration of an accelerator with aplurality of processing elements according to embodiments of thedisclosure.

FIG. 41 illustrates a snapshot of an in-flight, pipelined extractionaccording to embodiments of the disclosure.

FIG. 42 illustrates a compilation tool chain for an acceleratoraccording to embodiments of the disclosure.

FIG. 43 illustrates a compiler for an accelerator according toembodiments of the disclosure.

FIG. 44A illustrates sequential assembly code according to embodimentsof the disclosure.

FIG. 44B illustrates dataflow assembly code for the sequential assemblycode of FIG. 44A according to embodiments of the disclosure.

FIG. 44C illustrates a dataflow graph for the dataflow assembly code ofFIG. 44B for an accelerator according to embodiments of the disclosure.

FIG. 45A illustrates C source code according to embodiments of thedisclosure.

FIG. 45B illustrates dataflow assembly code for the C source code ofFIG. 45A according to embodiments of the disclosure.

FIG. 45C illustrates a dataflow graph for the dataflow assembly code ofFIG. 45B for an accelerator according to embodiments of the disclosure.

FIG. 46A illustrates C source code according to embodiments of thedisclosure.

FIG. 46B illustrates dataflow assembly code for the C source code ofFIG. 46A according to embodiments of the disclosure.

FIG. 46C illustrates a dataflow graph for the dataflow assembly code ofFIG. 46B for an accelerator according to embodiments of the disclosure.

FIG. 47A illustrates a flow diagram according to embodiments of thedisclosure.

FIG. 47B illustrates a flow diagram according to embodiments of thedisclosure.

FIG. 48 illustrates a throughput versus energy per operation graphaccording to embodiments of the disclosure.

FIG. 49 illustrates an accelerator tile comprising an array ofprocessing elements and a local configuration controller according toembodiments of the disclosure.

FIGS. 50A-50C illustrate a local configuration controller configuring adata path network according to embodiments of the disclosure.

FIG. 51 illustrates a configuration controller according to embodimentsof the disclosure.

FIG. 52 illustrates an accelerator tile comprising an array ofprocessing elements, a configuration cache, and a local configurationcontroller according to embodiments of the disclosure.

FIG. 53 illustrates an accelerator tile comprising an array ofprocessing elements and a configuration and exception handlingcontroller with a reconfiguration circuit according to embodiments ofthe disclosure.

FIG. 54 illustrates a reconfiguration circuit according to embodimentsof the disclosure.

FIG. 55 illustrates an accelerator tile comprising an array ofprocessing elements and a configuration and exception handlingcontroller with a reconfiguration circuit according to embodiments ofthe disclosure.

FIG. 56 illustrates an accelerator tile comprising an array ofprocessing elements and a mezzanine exception aggregator coupled to atile-level exception aggregator according to embodiments of thedisclosure.

FIG. 57 illustrates a processing element with an exception generatoraccording to embodiments of the disclosure.

FIG. 58 illustrates an accelerator tile comprising an array ofprocessing elements and a local extraction controller according toembodiments of the disclosure.

FIGS. 59A-59C illustrate a local extraction controller configuring adata path network according to embodiments of the disclosure.

FIG. 60 illustrates an extraction controller according to embodiments ofthe disclosure.

FIG. 61 illustrates a flow diagram according to embodiments of thedisclosure.

FIG. 62 illustrates a flow diagram according to embodiments of thedisclosure.

FIG. 63A is a block diagram of a system that employs a memory orderingcircuit interposed between a memory subsystem and acceleration hardwareaccording to embodiments of the disclosure.

FIG. 63B is a block diagram of the system of FIG. 63A, but which employsmultiple memory ordering circuits according to embodiments of thedisclosure.

FIG. 64 is a block diagram illustrating general functioning of memoryoperations into and out of acceleration hardware according toembodiments of the disclosure.

FIG. 65 is a block diagram illustrating a spatial dependency flow for astore operation according to embodiments of the disclosure.

FIG. 66 is a detailed block diagram of the memory ordering circuit ofFIG. 63 according to embodiments of the disclosure.

FIG. 67 is a flow diagram of a microarchitecture of the memory orderingcircuit of FIG. 63 according to embodiments of the disclosure.

FIG. 68 is a block diagram of an executable determiner circuit accordingto embodiments of the disclosure.

FIG. 69 is a block diagram of a priority encoder according toembodiments of the disclosure.

FIG. 70 is a block diagram of an exemplary load operation, both logicaland in binary according to embodiments of the disclosure.

FIG. 71A is flow diagram illustrating logical execution of an examplecode according to embodiments of the disclosure.

FIG. 71B is the flow diagram of FIG. 71A, illustrating memory-levelparallelism in an unfolded version of the example code according toembodiments of the disclosure.

FIG. 72A is a block diagram of exemplary memory arguments for a loadoperation and for a store operation according to embodiments of thedisclosure.

FIG. 72B is a block diagram illustrating flow of load operations and thestore operations, such as those of FIG. 72A, through themicroarchitecture of the memory ordering circuit of FIG. 67 according toembodiments of the disclosure.

FIGS. 73A, 73B, 73C, 73D, 73E, 73F, 73G, and 73H are block diagramsillustrating functional flow of load operations and store operations foran exemplary program through queues of the microarchitecture of FIG. 73Baccording to embodiments of the disclosure.

FIG. 74 is a flow chart of a method for ordering memory operationsbetween a acceleration hardware and an out-of-order memory subsystemaccording to embodiments of the disclosure.

FIG. 75A is a block diagram illustrating a generic vector friendlyinstruction format and class A instruction templates thereof accordingto embodiments of the disclosure.

FIG. 75B is a block diagram illustrating the generic vector friendlyinstruction format and class B instruction templates thereof accordingto embodiments of the disclosure.

FIG. 76A is a block diagram illustrating fields for the generic vectorfriendly instruction formats in FIGS. 75A and 75B according toembodiments of the disclosure.

FIG. 76B is a block diagram illustrating the fields of the specificvector friendly instruction format in FIG. 76A that make up a fullopcode field according to one embodiment of the disclosure.

FIG. 76C is a block diagram illustrating the fields of the specificvector friendly instruction format in FIG. 76A that make up a registerindex field according to one embodiment of the disclosure.

FIG. 76D is a block diagram illustrating the fields of the specificvector friendly instruction format in FIG. 76A that make up theaugmentation operation field 7550 according to one embodiment of thedisclosure.

FIG. 77 is a block diagram of a register architecture according to oneembodiment of the disclosure

FIG. 78A is a block diagram illustrating both an exemplary in-orderpipeline and an exemplary register renaming, out-of-orderissue/execution pipeline according to embodiments of the disclosure.

FIG. 78B is a block diagram illustrating both an exemplary embodiment ofan in-order architecture core and an exemplary register renaming,out-of-order issue/execution architecture core to be included in aprocessor according to embodiments of the disclosure.

FIG. 79A is a block diagram of a single processor core, along with itsconnection to the on-die interconnect network and with its local subsetof the Level 2 (L2) cache, according to embodiments of the disclosure.

FIG. 79B is an expanded view of part of the processor core in FIG. 79Aaccording to embodiments of the disclosure.

FIG. 80 is a block diagram of a processor that may have more than onecore, may have an integrated memory controller, and may have integratedgraphics according to embodiments of the disclosure.

FIG. 81 is a block diagram of a system in accordance with one embodimentof the present disclosure.

FIG. 82 is a block diagram of a more specific exemplary system inaccordance with an embodiment of the present disclosure.

FIG. 83, shown is a block diagram of a second more specific exemplarysystem in accordance with an embodiment of the present disclosure.

FIG. 84, shown is a block diagram of a system on a chip (SoC) inaccordance with an embodiment of the present disclosure.

FIG. 85 is a block diagram contrasting the use of a software instructionconverter to convert binary instructions in a source instruction set tobinary instructions in a target instruction set according to embodimentsof the disclosure.

DETAILED DESCRIPTION

In the following description, numerous specific details are set forth.However, it is understood that embodiments of the disclosure may bepracticed without these specific details. In other instances, well-knowncircuits, structures and techniques have not been shown in detail inorder not to obscure the understanding of this description.

References in the specification to “one embodiment,” “an embodiment,”“an example embodiment,” etc., indicate that the embodiment describedmay include a particular feature, structure, or characteristic, butevery embodiment may not necessarily include the particular feature,structure, or characteristic. Moreover, such phrases are not necessarilyreferring to the same embodiment. Further, when a particular feature,structure, or characteristic is described in connection with anembodiment, it is submitted that it is within the knowledge of oneskilled in the art to affect such feature, structure, or characteristicin connection with other embodiments whether or not explicitlydescribed.

A processor (e.g., having one or more cores) may execute instructions(e.g., a thread of instructions) to operate on data, for example, toperform arithmetic, logic, or other functions. For example, software mayrequest an operation and a hardware processor (e.g., a core or coresthereof) may perform the operation in response to the request. Onenon-limiting example of an operation is a blend operation to input aplurality of vectors elements and output a vector with a blendedplurality of elements. In certain embodiments, multiple operations areaccomplished with the execution of a single instruction.

Exascale performance, e.g., as defined by the Department of Energy, mayrequire system-level floating point performance to exceed 10{circumflexover ( )}18 floating point operations per second (exaFLOPs) or morewithin a given (e.g., 20 MW) power budget. Certain embodiments hereinare directed to a spatial array of processing elements (e.g., aconfigurable spatial accelerator (CSA)) that targets high performancecomputing (HPC), for example, of a processor. Certain embodiments hereinof a spatial array of processing elements (e.g., a CSA) target thedirect execution of a dataflow graph to yield a computationally denseyet energy-efficient spatial microarchitecture which far exceedsconventional roadmap architectures. Certain embodiments herein providefor distributed coordination for distributed structures (e.g.,distributed TLBs), e.g., in contrast to a local management circuit. Asdiscussed further below, embodiments herein include unified translationlookaside buffer (TLB) management hardware or distributed translationlookaside buffer (TLB) management hardware, e.g., for a shared virtualmemory.

Below also includes a description of the architectural philosophy ofembodiments of a spatial array of processing elements (e.g., a CSA) andcertain features thereof. As with any revolutionary architecture,programmability may be a risk. To mitigate this issue, embodiments ofthe CSA architecture have been co-designed with a compilation toolchain, which is also discussed below.

INTRODUCTION

Exascale computing goals may require enormous system-level floatingpoint performance (e.g., 1 ExaFLOPs) within an aggressive power budget(e.g., 20 MW). However, simultaneously improving the performance andenergy efficiency of program execution with classical von Neumannarchitectures has become difficult: out-of-order scheduling,simultaneous multi-threading, complex register files, and otherstructures provide performance, but at high energy cost. Certainembodiments herein achieve performance and energy requirementssimultaneously. Exascale computing power-performance targets may demandboth high throughput and low energy consumption per operation. Certainembodiments herein provide this by providing for large numbers oflow-complexity, energy-efficient processing (e.g., computational)elements which largely eliminate the control overheads of previousprocessor designs. Guided by this observation, certain embodimentsherein include a spatial array of processing elements, for example, aconfigurable spatial accelerator (CSA), e.g., comprising an array ofprocessing elements (PEs) connected by a set of light-weight,back-pressured (e.g., communication) networks. One example of a CSA tileis depicted in FIG. 1. Certain embodiments of processing (e.g., compute)elements are dataflow operators, e.g., multiple of a dataflow operatorthat only processes input data when both (i) the input data has arrivedat the dataflow operator and (ii) there is space available for storingthe output data, e.g., otherwise no processing is occurring. Certainembodiments (e.g., of an accelerator or CSA) do not utilize a triggeredinstruction.

FIG. 1 illustrates an accelerator tile 100 embodiment of a spatial arrayof processing elements according to embodiments of the disclosure.Accelerator tile 100 may be a portion of a larger tile. Accelerator tile100 executes a dataflow graph or graphs. A dataflow graph may generallyrefer to an explicitly parallel program description which arises in thecompilation of sequential codes. Certain embodiments herein (e.g., CSAs)allow dataflow graphs to be directly configured onto the CSA array, forexample, rather than being transformed into sequential instructionstreams. Certain embodiments herein allow a first (e.g., type of)dataflow operation to be performed by one or more processing elements(PEs) of the spatial array and, additionally or alternatively, a second(e.g., different, type of) dataflow operation to be performed by one ormore of the network communication circuits (e.g., endpoints) of thespatial array.

The derivation of a dataflow graph from a sequential compilation flowallows embodiments of a CSA to support familiar programming models andto directly (e.g., without using a table of work) execute existing highperformance computing (HPC) code. CSA processing elements (PEs) may beenergy efficient. In FIG. 1, memory interface 102 may couple to a memory(e.g., memory 202 in FIG. 2) to allow accelerator tile 100 to access(e.g., load and/store) data to the (e.g., off die) memory. Depictedaccelerator tile 100 is a heterogeneous array comprised of several kindsof PEs coupled together via an interconnect network 104. Acceleratortile 100 may include one or more of integer arithmetic PEs, floatingpoint arithmetic PEs, communication circuitry (e.g., network dataflowendpoint circuits), and in-fabric storage, e.g., as part of spatialarray of processing elements 101. Dataflow graphs (e.g., compileddataflow graphs) may be overlaid on the accelerator tile 100 forexecution. In one embodiment, for a particular dataflow graph, each PEhandles only one or two (e.g., dataflow) operations of the graph. Thearray of PEs may be heterogeneous, e.g., such that no PE supports thefull CSA dataflow architecture and/or one or more PEs are programmed(e.g., customized) to perform only a few, but highly efficientoperations. Certain embodiments herein thus yield a processor oraccelerator having an array of processing elements that iscomputationally dense compared to roadmap architectures and yet achievesapproximately an order-of-magnitude gain in energy efficiency andperformance relative to existing HPC offerings.

Certain embodiments herein provide for performance increases fromparallel execution within a (e.g., dense) spatial array of processingelements (e.g., CSA) where each PE and/or network dataflow endpointcircuit utilized may perform its operations simultaneously, e.g., ifinput data is available. Efficiency increases may result from theefficiency of each PE and/or network dataflow endpoint circuit, e.g.,where each PE's operation (e.g., behavior) is fixed once perconfiguration (e.g., mapping) step and execution occurs on local dataarrival at the PE, e.g., without considering other fabric activity,and/or where each network dataflow endpoint circuit's operation (e.g.,behavior) is variable (e.g., not fixed) when configured (e.g., mapped).In certain embodiments, a PE and/or network dataflow endpoint circuit is(e.g., each a single) dataflow operator, for example, a dataflowoperator that only operates on input data when both (i) the input datahas arrived at the dataflow operator and (ii) there is space availablefor storing the output data, e.g., otherwise no operation is occurring.

Certain embodiments herein include a spatial array of processingelements as an energy-efficient and high-performance way of acceleratinguser applications. In one embodiment, applications are mapped in anextremely parallel manner. For example, inner loops may be unrolledmultiple times to improve parallelism. This approach may provide highperformance, e.g., when the occupancy (e.g., use) of the unrolled codeis high. However, if there are less used code paths in the loop bodyunrolled (for example, an exceptional code path like floating pointde-normalized mode) then (e.g., fabric area of) the spatial array ofprocessing elements may be wasted and throughput consequently lost.

One embodiment herein to reduce pressure on (e.g., fabric area of) thespatial array of processing elements (e.g., in the case of underutilizedcode segments) is time multiplexing. In this mode, a single instance ofthe less used (e.g., colder) code may be shared among several loopbodies, for example, analogous to a function call in a shared library.In one embodiment, spatial arrays (e.g., of processing elements) supportthe direct implementation of multiplexed codes. However, e.g., whenmultiplexing or demultiplexing in a spatial array involves choosingamong many and distant targets (e.g., sharers), a direct implementationusing dataflow operators (e.g., using the processing elements) may beinefficient in terms of latency, throughput, implementation area, and/orenergy. Certain embodiments herein describe hardware mechanisms (e.g.,network circuitry) supporting (e.g., high-radix) multiplexing ordemultiplexing. Certain embodiments herein (e.g., of network dataflowendpoint circuits) permit the aggregation of many targets (e.g.,sharers) with little hardware overhead or performance impact. Certainembodiments herein allow for compiling of (e.g., legacy) sequentialcodes to parallel architectures in a spatial array.

In one embodiment, a plurality of network dataflow endpoint circuitscombine as a single dataflow operator, for example, as discussed inreference to FIG. 13 below. As non-limiting examples, certain (forexample, high (e.g., 4-6) radix) dataflow operators are listed below.

An embodiment of a “Pick” dataflow operator is to select data (e.g., atoken) from a plurality of input channels and provide that data as its(e.g., single) output according to control data. Control data for a Pickmay include an input selector value. In one embodiment, the selectedinput channel is to have its data (e.g., token) removed (e.g.,discarded), for example, to complete the performance of that dataflowoperation (or its portion of a dataflow operation). In one embodiment,additionally, those non-selected input channels are also to have theirdata (e.g., token) removed (e.g., discarded), for example, to completethe performance of that dataflow operation (or its portion of a dataflowoperation).

An embodiment of a “PickSingleLeg” dataflow operator is to select data(e.g., a token) from a plurality of input channels and provide that dataas its (e.g., single) output according to control data, but in certainembodiments, the non-selected input channels are ignored, e.g., thosenon-selected input channels are not to have their data (e.g., token)removed (e.g., discarded), for example, to complete the performance ofthat dataflow operation (or its portion of a dataflow operation).Control data for a PickSingleLeg may include an input selector value. Inone embodiment, the selected input channel is also to have its data(e.g., token) removed (e.g., discarded), for example, to complete theperformance of that dataflow operation (or its portion of a dataflowoperation).

An embodiment of a “PickAny” dataflow operator is to select the firstavailable (e.g., to the circuit performing the operation) data (e.g., atoken) from a plurality of input channels and provide that data as its(e.g., single) output. In one embodiment, PickSingleLeg is also tooutput the index (e.g., indicating which of the plurality of inputchannels) had its data selected. In one embodiment, the selected inputchannel is to have its data (e.g., token) removed (e.g., discarded), forexample, to complete the performance of that dataflow operation (or itsportion of a dataflow operation). In certain embodiments, thenon-selected input channels (e.g., with or without input data) areignored, e.g., those non-selected input channels are not to have theirdata (e.g., token) removed (e.g., discarded), for example, to completethe performance of that dataflow operation (or its portion of a dataflowoperation). Control data for a PickAny may include a value correspondingto the PickAny, e.g., without an input selector value.

An embodiment of a “Switch” dataflow operator is to steer (e.g., single)input data (e.g., a token) so as to provide that input data to one or aplurality of (e.g., less than all) outputs according to control data.Control data for a Switch may include an output(s) selector value orvalues. In one embodiment, the input data (e.g., from an input channel)is to have its data (e.g., token) removed (e.g., discarded), forexample, to complete the performance of that dataflow operation (or itsportion of a dataflow operation).

An embodiment of a “SwitchAny” dataflow operator is to steer (e.g.,single) input data (e.g., a token) so as to provide that input data toone or a plurality of (e.g., less than all) outputs that may receivethat data, e.g., according to control data. In one embodiment, SwitchAnymay provide the input data to any coupled output channel that hasavailability (e.g., available storage space) in its ingress buffer,e.g., network ingress buffer in FIG. 14. Control data for a SwitchAnymay include a value corresponding to the SwitchAny, e.g., without anoutput(s) selector value or values. In one embodiment, the input data(e.g., from an input channel) is to have its data (e.g., token) removed(e.g., discarded), for example, to complete the performance of thatdataflow operation (or its portion of a dataflow operation). In oneembodiment, SwitchAny is also to output the index (e.g., indicatingwhich of the plurality of output channels) that it provided (e.g., sent)the input data to. SwitchAny may be utilized to manage replicatedsub-graphs in a spatial array, for example, an unrolled loop.

Certain embodiments herein thus provide paradigm-shifting levels ofperformance and tremendous improvements in energy efficiency across abroad class of existing single-stream and parallel programs, e.g., allwhile preserving familiar HPC programming models. Certain embodimentsherein may target HPC such that floating point energy efficiency isextremely important. Certain embodiments herein not only delivercompelling improvements in performance and reductions in energy, theyalso deliver these gains to existing HPC programs written in mainstreamHPC languages and for mainstream HPC frameworks. Certain embodiments ofthe architecture herein (e.g., with compilation in mind) provide severalextensions in direct support of the control-dataflow internalrepresentations generated by modern compilers. Certain embodimentsherein are direct to a CSA dataflow compiler, e.g., which can accept C,C++, and Fortran programming languages, to target a CSA architecture.

FIG. 2 illustrates a hardware processor 200 coupled to (e.g., connectedto) a memory 202 according to embodiments of the disclosure. In oneembodiment, hardware processor 200 and memory 202 are a computing system201. In certain embodiments, one or more of accelerators is a CSAaccording to this disclosure. In certain embodiments, one or more of thecores in a processor are those cores disclosed herein. Hardwareprocessor 200 (e.g., each core thereof) may include a hardware decoder(e.g., decode unit) and a hardware execution unit. Hardware processor200 may include registers. Note that the figures herein may not depictall data communication couplings (e.g., connections). One of ordinaryskill in the art will appreciate that this is to not obscure certaindetails in the figures. Note that a double headed arrow in the figuresmay not require two-way communication, for example, it may indicateone-way communication (e.g., to or from that component or device). Anyor all combinations of communications paths may be utilized in certainembodiments herein. Depicted hardware processor 200 includes a pluralityof cores (o to N, where N may be 1 or more) and hardware accelerators (oto M, where M may be 1 or more) according to embodiments of thedisclosure. Hardware processor 200 (e.g., accelerator(s) and/or core(s)thereof) may be coupled to memory 202 (e.g., data storage device).Hardware decoder (e.g., of core) may receive an (e.g., single)instruction (e.g., macro-instruction) and decode the instruction, e.g.,into micro-instructions and/or micro-operations. Hardware execution unit(e.g., of core) may execute the decoded instruction (e.g.,macro-instruction) to perform an operation or operations.

Section 1 below discloses embodiments of CSA architecture. Inparticular, novel embodiments of integrating memory within the dataflowexecution model are disclosed. Section 2 delves into themicroarchitectural details of embodiments of a CSA. In one embodiment,the main goal of a CSA is to support compiler produced programs. Section3 below examines embodiments of a CSA compilation tool chain. Theadvantages of embodiments of a CSA are compared to other architecturesin the execution of compiled codes in Section 4. Finally the performanceof embodiments of a CSA microarchitecture is discussed in Section 5,further CSA details are discussed in Section 6, and a summary isprovided in Section 7.

1. CSA Architecture

The goal of certain embodiments of a CSA is to rapidly and efficientlyexecute programs, e.g., programs produced by compilers. Certainembodiments of the CSA architecture provide programming abstractionsthat support the needs of compiler technologies and programmingparadigms. Embodiments of the CSA execute dataflow graphs, e.g., aprogram manifestation that closely resembles the compiler's own internalrepresentation (IR) of compiled programs. In this model, a program isrepresented as a dataflow graph comprised of nodes (e.g., vertices)drawn from a set of architecturally-defined dataflow operators (e.g.,that encompass both computation and control operations) and edges whichrepresent the transfer of data between dataflow operators. Execution mayproceed by injecting dataflow tokens (e.g., that are or represent datavalues) into the dataflow graph. Tokens may flow between and betransformed at each node (e.g., vertex), for example, forming a completecomputation. A sample dataflow graph and its derivation from high-levelsource code is shown in FIGS. 3A-3C, and FIG. 5 shows an example of theexecution of a dataflow graph.

Embodiments of the CSA are configured for dataflow graph execution byproviding exactly those dataflow-graph-execution supports required bycompilers. In one embodiment, the CSA is an accelerator (e.g., anaccelerator in FIG. 2) and it does not seek to provide some of thenecessary but infrequently used mechanisms available on general purposeprocessing cores (e.g., a core in FIG. 2), such as system calls.Therefore, in this embodiment, the CSA can execute many codes, but notall codes. In exchange, the CSA gains significant performance and energyadvantages. To enable the acceleration of code written in commonly usedsequential languages, embodiments herein also introduce several novelarchitectural features to assist the compiler. One particular novelty isCSA's treatment of memory, a subject which has been ignored or poorlyaddressed previously. Embodiments of the CSA are also unique in the useof dataflow operators, e.g., as opposed to lookup tables (LUTs), astheir fundamental architectural interface.

Turning to embodiments of the CSA, dataflow operators are discussednext.

1.1 Dataflow Operators

The key architectural interface of embodiments of the accelerator (e.g.,CSA) is the dataflow operator, e.g., as a direct representation of anode in a dataflow graph. From an operational perspective, dataflowoperators behave in a streaming or data-driven fashion. Dataflowoperators may execute as soon as their incoming operands becomeavailable. CSA dataflow execution may depend (e.g., only) on highlylocalized status, for example, resulting in a highly scalablearchitecture with a distributed, asynchronous execution model. Dataflowoperators may include arithmetic dataflow operators, for example, one ormore of floating point addition and multiplication, integer addition,subtraction, and multiplication, various forms of comparison, logicaloperators, and shift. However, embodiments of the CSA may also include arich set of control operators which assist in the management of dataflowtokens in the program graph. Examples of these include a “pick”operator, e.g., which multiplexes two or more logical input channelsinto a single output channel, and a “switch” operator, e.g., whichoperates as a channel demultiplexor (e.g., outputting a single channelfrom two or more logical input channels). These operators may enable acompiler to implement control paradigms such as conditional expressions.Certain embodiments of a CSA may include a limited dataflow operator set(e.g., to relatively small number of operations) to yield dense andenergy efficient PE microarchitectures. Certain embodiments may includedataflow operators for complex operations that are common in HPC code.The CSA dataflow operator architecture is highly amenable todeployment-specific extensions. For example, more complex mathematicaldataflow operators, e.g., trigonometry functions, may be included incertain embodiments to accelerate certain mathematics-intensive HPCworkloads. Similarly, a neural-network tuned extension may includedataflow operators for vectorized, low precision arithmetic.

FIG. 3A illustrates a program source according to embodiments of thedisclosure. Program source code includes a multiplication function(func). FIG. 3B illustrates a dataflow graph 300 for the program sourceof FIG. 3A according to embodiments of the disclosure. Dataflow graph300 includes a pick node 304, switch node 306, and multiplication node308. A buffer may optionally be included along one or more of thecommunication paths. Depicted dataflow graph 300 may perform anoperation of selecting input X with pick node 304, multiplying X by Y(e.g., multiplication node 308), and then outputting the result from theleft output of the switch node 306. FIG. 3C illustrates an accelerator(e.g., CSA) with a plurality of processing elements 301 configured toexecute the dataflow graph of FIG. 3B according to embodiments of thedisclosure. More particularly, the dataflow graph 300 is overlaid intothe array of processing elements 301 (e.g., and the (e.g., interconnect)network(s) therebetween), for example, such that each node of thedataflow graph 300 is represented as a dataflow operator in the array ofprocessing elements 301. For example, certain dataflow operations may beachieved with a processing element and/or certain dataflow operationsmay be achieved with a communications network (e.g., a network dataflowendpoint circuit thereof). For example, a Pick, PickSingleLeg, PickAny,Switch, and/or SwitchAny operation may be achieved with one or morecomponents of a communications network (e.g., a network dataflowendpoint circuit thereof), e.g., in contrast to a processing element.

In one embodiment, one or more of the processing elements in the arrayof processing elements 301 is to access memory through memory interface302. In one embodiment, pick node 304 of dataflow graph 300 thuscorresponds (e.g., is represented by) to pick operator 304A, switch node306 of dataflow graph 300 thus corresponds (e.g., is represented by) toswitch operator 306A, and multiplier node 308 of dataflow graph 300 thuscorresponds (e.g., is represented by) to multiplier operator 308A.Another processing element and/or a flow control path network mayprovide the control signals (e.g., control tokens) to the pick operator304A and switch operator 306A to perform the operation in FIG. 3A. Inone embodiment, array of processing elements 301 is configured toexecute the dataflow graph 300 of FIG. 3B before execution begins. Inone embodiment, compiler performs the conversion from FIG. 3A-3B. In oneembodiment, the input of the dataflow graph nodes into the array ofprocessing elements logically embeds the dataflow graph into the arrayof processing elements, e.g., as discussed further below, such that theinput/output paths are configured to produce the desired result.

1.2 Latency Insensitive Channels

Communications arcs are the second major component of the dataflowgraph. Certain embodiments of a CSA describes these arcs as latencyinsensitive channels, for example, in-order, back-pressured (e.g., notproducing or sending output until there is a place to store the output),point-to-point communications channels. As with dataflow operators,latency insensitive channels are fundamentally asynchronous, giving thefreedom to compose many types of networks to implement the channels of aparticular graph. Latency insensitive channels may have arbitrarily longlatencies and still faithfully implement the CSA architecture. However,in certain embodiments there is strong incentive in terms of performanceand energy to make latencies as small as possible. Section 2.2 hereindiscloses a network microarchitecture in which dataflow graph channelsare implemented in a pipelined fashion with no more than one cycle oflatency. Embodiments of latency-insensitive channels provide a criticalabstraction layer which may be leveraged with the CSA architecture toprovide a number of runtime services to the applications programmer. Forexample, a CSA may leverage latency-insensitive channels in theimplementation of the CSA configuration (the loading of a program ontothe CSA array).

FIG. 4 illustrates an example execution of a dataflow graph 400according to embodiments of the disclosure. At step 1, input values(e.g., 1 for X in FIG. 3B and 2 for Y in FIG. 3B) may be loaded indataflow graph 400 to perform a 1*2 multiplication operation. One ormore of the data input values may be static (e.g., constant) in theoperation (e.g., 1 for X and 2 for Y in reference to FIG. 3B) or updatedduring the operation. At step 2, a processing element (e.g., on a flowcontrol path network) or other circuit outputs a zero to control input(e.g., multiplexer control signal) of pick node 404 (e.g., to source aone from port “0” to its output) and outputs a zero to control input(e.g., multiplexer control signal) of switch node 406 (e.g., to provideits input out of port “0” to a destination (e.g., a downstreamprocessing element). At step 3, the data value of 1 is output from picknode 404 (e.g., and consumes its control signal “0” at the pick node404) to multiplier node 408 to be multiplied with the data value of 2 atstep 4. At step 4, the output of multiplier node 408 arrives at switchnode 406, e.g., which causes switch node 406 to consume a control signal“0” to output the value of 2 from port “0” of switch node 406 at step 5.The operation is then complete. A CSA may thus be programmed accordinglysuch that a corresponding dataflow operator for each node performs theoperations in FIG. 4. Although execution is serialized in this example,in principle all dataflow operations may execute in parallel. Steps areused in FIG. 4 to differentiate dataflow execution from any physicalmicroarchitectural manifestation. In one embodiment a downstreamprocessing element is to send a signal (or not send a ready signal) (forexample, on a flow control path network) to the switch 406 to stall theoutput from the switch 406, e.g., until the downstream processingelement is ready (e.g., has storage room) for the output.

1.3 Memory

Dataflow architectures generally focus on communication and datamanipulation with less attention paid to state. However, enabling realsoftware, especially programs written in legacy sequential languages,requires significant attention to interfacing with memory. Certainembodiments of a CSA use architectural memory operations as theirprimary interface to (e.g., large) stateful storage. From theperspective of the dataflow graph, memory operations are similar toother dataflow operations, except that they have the side effect ofupdating a shared store. In particular, memory operations of certainembodiments herein have the same semantics as every other dataflowoperator, for example, they “execute” when their operands, e.g., anaddress, are available and, after some latency, a response is produced.Certain embodiments herein explicitly decouple the operand input andresult output such that memory operators are naturally pipelined andhave the potential to produce many simultaneous outstanding requests,e.g., making them exceptionally well suited to the latency and bandwidthcharacteristics of a memory subsystem. Embodiments of a CSA providebasic memory operations such as load, which takes an address channel andpopulates a response channel with the values corresponding to theaddresses, and a store. Embodiments of a CSA may also provide moreadvanced operations such as in-memory atomics and consistency operators.These operations may have similar semantics to their von Neumanncounterparts. Embodiments of a CSA may accelerate existing programsdescribed using sequential languages such as C and Fortran. Aconsequence of supporting these language models is addressing programmemory order, e.g., the serial ordering of memory operations typicallyprescribed by these languages.

FIG. 5 illustrates a program source (e.g., C code) 500 according toembodiments of the disclosure. According to the memory semantics of theC programming language, memory copy (memcpy) should be serialized.However, memcpy may be parallelized with an embodiment of the CSA ifarrays A and B are known to be disjoint. FIG. 5 further illustrates theproblem of program order. In general, compilers cannot prove that arrayA is different from array B, e.g., either for the same value of index ordifferent values of index across loop bodies. This is known as pointeror memory aliasing. Since compilers are to generate statically correctcode, they are usually forced to serialize memory accesses. Typically,compilers targeting sequential von Neumann architectures use instructionordering as a natural means of enforcing program order. However,embodiments of the CSA have no notion of instruction orinstruction-based program ordering as defined by a program counter. Incertain embodiments, incoming dependency tokens, e.g., which contain noarchitecturally visible information, are like all other dataflow tokensand memory operations may not execute until they have received adependency token. In certain embodiments, memory operations produce anoutgoing dependency token once their operation is visible to alllogically subsequent, dependent memory operations. In certainembodiments, dependency tokens are similar to other dataflow tokens in adataflow graph. For example, since memory operations occur inconditional contexts, dependency tokens may also be manipulated usingcontrol operators described in Section 1.1, e.g., like any other tokens.Dependency tokens may have the effect of serializing memory accesses,e.g., providing the compiler a means of architecturally defining theorder of memory accesses.

1.4 Runtime Services

A primary architectural considerations of embodiments of the CSA involvethe actual execution of user-level programs, but it may also bedesirable to provide several support mechanisms which underpin thisexecution. Chief among these are configuration (in which a dataflowgraph is loaded into the CSA), extraction (in which the state of anexecuting graph is moved to memory), and exceptions (in whichmathematical, soft, and other types of errors in the fabric are detectedand handled, possibly by an external entity). Section 2.8 belowdiscusses the properties of a latency-insensitive dataflow architectureof an embodiment of a CSA to yield efficient, largely pipelinedimplementations of these functions. Conceptually, configuration may loadthe state of a dataflow graph into the interconnect (and/orcommunications network (e.g., a network dataflow endpoint circuitthereof)) and processing elements (e.g., fabric), e.g., generally frommemory. During this step, all structures in the CSA may be loaded with anew dataflow graph and any dataflow tokens live in that graph, forexample, as a consequence of a context switch. The latency-insensitivesemantics of a CSA may permit a distributed, asynchronous initializationof the fabric, e.g., as soon as PEs are configured, they may beginexecution immediately. Unconfigured PEs may backpressure their channelsuntil they are configured, e.g., preventing communications betweenconfigured and unconfigured elements. The CSA configuration may bepartitioned into privileged and user-level state. Such a two-levelpartitioning may enable primary configuration of the fabric to occurwithout invoking the operating system. During one embodiment ofextraction, a logical view of the dataflow graph is captured andcommitted into memory, e.g., including all live control and dataflowtokens and state in the graph.

Extraction may also play a role in providing reliability guaranteesthrough the creation of fabric checkpoints. Exceptions in a CSA maygenerally be caused by the same events that cause exceptions inprocessors, such as illegal operator arguments or reliability,availability, and serviceability (RAS) events. In certain embodiments,exceptions are detected at the level of dataflow operators, for example,checking argument values or through modular arithmetic schemes. Upondetecting an exception, a dataflow operator (e.g., circuit) may halt andemit an exception message, e.g., which contains both an operationidentifier and some details of the nature of the problem that hasoccurred. In one embodiment, the dataflow operator will remain halteduntil it has been reconfigured. The exception message may then becommunicated to an associated processor (e.g., core) for service, e.g.,which may include extracting the graph for software analysis.

1.5 Tile-level Architecture

Embodiments of the CSA computer architectures (e.g., targeting HPC anddatacenter uses) are tiled. FIGS. 6 and 8 show tile-level deployments ofa CSA. FIG. 8 shows a full-tile implementation of a CSA, e.g., which maybe an accelerator of a processor with a core. A main advantage of thisarchitecture is may be reduced design risk, e.g., such that the CSA andcore are completely decoupled in manufacturing. In addition to allowingbetter component reuse, this may allow the design of components like theCSA Cache to consider only the CSA, e.g., rather than needing toincorporate the stricter latency requirements of the core. Finally,separate tiles may allow for the integration of CSA with small or largecores. One embodiment of the CSA captures most vector-parallel workloadssuch that most vector-style workloads run directly on the CSA, but incertain embodiments vector-style instructions in the core may beincluded, e.g., to support legacy binaries.

2. Microarchitecture

In one embodiment, the goal of the CSA microarchitecture is to provide ahigh quality implementation of each dataflow operator specified by theCSA architecture. Embodiments of the CSA microarchitecture provide thateach processing element (and/or communications network (e.g., a networkdataflow endpoint circuit thereof)) of the microarchitecture correspondsto approximately one node (e.g., entity) in the architectural dataflowgraph. In one embodiment, a node in the dataflow graph is distributed inmultiple network dataflow endpoint circuits. In certain embodiments,this results in microarchitectural elements that are not only compact,resulting in a dense computation array, but also energy efficient, forexample, where processing elements (PEs) are both simple and largelyunmultiplexed, e.g., executing a single dataflow operator for aconfiguration (e.g., programming) of the CSA. To further reduce energyand implementation area, a CSA may include a configurable, heterogeneousfabric style in which each PE thereof implements only a subset ofdataflow operators (e.g., with a separate subset of dataflow operatorsimplemented with network dataflow endpoint circuit(s)). Peripheral andsupport subsystems, such as the CSA cache, may be provisioned to supportthe distributed parallelism incumbent in the main CSA processing fabricitself. Implementation of CSA microarchitectures may utilize dataflowand latency-insensitive communications abstractions present in thearchitecture. In certain embodiments, there is (e.g., substantially) aone-to-one correspondence between nodes in the compiler generated graphand the dataflow operators (e.g., dataflow operator compute elements) ina CSA.

Below is a discussion of an example CSA, followed by a more detaileddiscussion of the microarchitecture. Certain embodiments herein providea CSA that allows for easy compilation, e.g., in contrast to an existingFPGA compilers that handle a small subset of a programming language(e.g., C or C++) and require many hours to compile even small programs.

Certain embodiments of a CSA architecture admits of heterogeneouscoarse-grained operations, like double precision floating point.Programs may be expressed in fewer coarse grained operations, e.g., suchthat the disclosed compiler runs faster than traditional spatialcompilers. Certain embodiments include a fabric with new processingelements to support sequential concepts like program ordered memoryaccesses. Certain embodiments implement hardware to supportcoarse-grained dataflow-style communication channels. This communicationmodel is abstract, and very close to the control-dataflow representationused by the compiler. Certain embodiments herein include a networkimplementation that supports single-cycle latency communications, e.g.,utilizing (e.g., small) PEs which support single control-dataflowoperations. In certain embodiments, not only does this improve energyefficiency and performance, it simplifies compilation because thecompiler makes a one-to-one mapping between high-level dataflowconstructs and the fabric. Certain embodiments herein thus simplify thetask of compiling existing (e.g., C, C++, or Fortran) programs to a CSA(e.g., fabric).

Energy efficiency may be a first order concern in modern computersystems. Certain embodiments herein provide a new schema ofenergy-efficient spatial architectures. In certain embodiments, thesearchitectures form a fabric with a unique composition of a heterogeneousmix of small, energy-efficient, data-flow oriented processing elements(PEs) (and/or a packet switched communications network (e.g., a networkdataflow endpoint circuit thereof)) with a lightweight circuit switchedcommunications network (e.g., interconnect), e.g., with hardened supportfor flow control. Due to the energy advantages of each, the combinationof these components may form a spatial accelerator (e.g., as part of acomputer) suitable for executing compiler-generated parallel programs inan extremely energy efficient manner. Since this fabric isheterogeneous, certain embodiments may be customized for differentapplication domains by introducing new domain-specific PEs. For example,a fabric for high-performance computing might include some customizationfor double-precision, fused multiply-add, while a fabric targeting deepneural networks might include low-precision floating point operations.

An embodiment of a spatial architecture schema, e.g., as exemplified inFIG. 6, is the composition of light-weight processing elements (PE)connected by an inter-PE network. Generally, PEs may comprise dataflowoperators, e.g., where once (e.g., all) input operands arrive at thedataflow operator, some operation (e.g., micro-instruction or set ofmicro-instructions) is executed, and the results are forwarded todownstream operators. Control, scheduling, and data storage maytherefore be distributed amongst the PEs, e.g., removing the overhead ofthe centralized structures that dominate classical processors.

Programs may be converted to dataflow graphs that are mapped onto thearchitecture by configuring PEs and the network to express thecontrol-dataflow graph of the program. Communication channels may beflow-controlled and fully back-pressured, e.g., such that PEs will stallif either source communication channels have no data or destinationcommunication channels are full. In one embodiment, at runtime, dataflow through the PEs and channels that have been configured to implementthe operation (e.g., an accelerated algorithm). For example, data may bestreamed in from memory, through the fabric, and then back out tomemory.

Embodiments of such an architecture may achieve remarkable performanceefficiency relative to traditional multicore processors: compute (e.g.,in the form of PEs) may be simpler, more energy efficient, and moreplentiful than in larger cores, and communications may be direct andmostly short-haul, e.g., as opposed to occurring over a wide, full-chipnetwork as in typical multicore processors. Moreover, becauseembodiments of the architecture are extremely parallel, a number ofpowerful circuit and device level optimizations are possible withoutseriously impacting throughput, e.g., low leakage devices and lowoperating voltage. These lower-level optimizations may enable evengreater performance advantages relative to traditional cores. Thecombination of efficiency at the architectural, circuit, and devicelevels yields of these embodiments are compelling. Embodiments of thisarchitecture may enable larger active areas as transistor densitycontinues to increase.

Embodiments herein offer a unique combination of dataflow support andcircuit switching to enable the fabric to be smaller, moreenergy-efficient, and provide higher aggregate performance as comparedto previous architectures. FPGAs are generally tuned towardsfine-grained bit manipulation, whereas embodiments herein are tunedtoward the double-precision floating point operations found in HPCapplications. Certain embodiments herein may include a FPGA in additionto a CSA according to this disclosure.

Certain embodiments herein combine a light-weight network with energyefficient dataflow processing elements (and/or communications network(e.g., a network dataflow endpoint circuit thereof)) to form ahigh-throughput, low-latency, energy-efficient HPC fabric. Thislow-latency network may enable the building of processing elements(and/or communications network (e.g., a network dataflow endpointcircuit thereof)) with fewer functionalities, for example, only one ortwo instructions and perhaps one architecturally visible register, sinceit is efficient to gang multiple PEs together to form a completeprogram.

Relative to a processor core, CSA embodiments herein may provide formore computational density and energy efficiency. For example, when PEsare very small (e.g., compared to a core), the CSA may perform many moreoperations and have much more computational parallelism than a core,e.g., perhaps as many as 16 times the number of FMAs as a vectorprocessing unit (VPU). To utilize all of these computational elements,the energy per operation is very low in certain embodiments.

The energy advantages our embodiments of this dataflow architecture aremany. Parallelism is explicit in dataflow graphs and embodiments of theCSA architecture spend no or minimal energy to extract it, e.g., unlikeout-of-order processors which must re-discover parallelism each time aninstruction is executed. Since each PE is responsible for a singleoperation in one embodiment, the register files and ports counts may besmall, e.g., often only one, and therefore use less energy than theircounterparts in core. Certain CSAs include many PEs, each of which holdslive program values, giving the aggregate effect of a huge register filein a traditional architecture, which dramatically reduces memoryaccesses. In embodiments where the memory is multi-ported anddistributed, a CSA may sustain many more outstanding memory requests andutilize more bandwidth than a core. These advantages may combine toyield an energy level per watt that is only a small percentage over thecost of the bare arithmetic circuitry. For example, in the case of aninteger multiply, a CSA may consume no more than 25% more energy thanthe underlying multiplication circuit. Relative to one embodiment of acore, an integer operation in that CSA fabric consumes less than 1/30thof the energy per integer operation.

From a programming perspective, the application-specific malleability ofembodiments of the CSA architecture yields significant advantages over avector processing unit (VPU). In traditional, inflexible architectures,the number of functional units, like floating divide or the varioustranscendental mathematical functions, must be chosen at design timebased on some expected use case. In embodiments of the CSA architecture,such functions may be configured (e.g., by a user and not amanufacturer) into the fabric based on the requirement of eachapplication. Application throughput may thereby be further increased.Simultaneously, the compute density of embodiments of the CSA improvesby avoiding hardening such functions, and instead provision moreinstances of primitive functions like floating multiplication. Theseadvantages may be significant in HPC workloads, some of which spend 75%of floating execution time in transcendental functions.

Certain embodiments of the CSA represents a significant advance as adataflow-oriented spatial architectures, e.g., the PEs of thisdisclosure may be smaller, but also more energy-efficient. Theseimprovements may directly result from the combination ofdataflow-oriented PEs with a lightweight, circuit switched interconnect,for example, which has single-cycle latency, e.g., in contrast to apacket switched network (e.g., with, at a minimum, a 300% higherlatency). Certain embodiments of PEs support 32-bit or 64-bit operation.Certain embodiments herein permit the introduction of newapplication-specific PEs, for example, for machine learning or security,and not merely a homogeneous combination. Certain embodiments hereincombine lightweight dataflow-oriented processing elements with alightweight, low-latency network to form an energy efficientcomputational fabric.

In order for certain spatial architectures to be successful, programmersare to configure them with relatively little effort, e.g., whileobtaining significant power and performance superiority over sequentialcores. Certain embodiments herein provide for a CSA (e.g., spatialfabric) that is easily programmed (e.g., by a compiler), powerefficient, and highly parallel. Certain embodiments herein provide for a(e.g., interconnect) network that achieves these three goals. From aprogrammability perspective, certain embodiments of the network provideflow controlled channels, e.g., which correspond to the control-dataflowgraph (CDFG) model of execution used in compilers. Certain networkembodiments utilize dedicated, circuit switched links, such that programperformance is easier to reason about, both by a human and a compiler,because performance is predictable. Certain network embodiments offerboth high bandwidth and low latency. Certain network embodiments (e.g.,static, circuit switching) provides a latency of 0 to 1 cycle (e.g.,depending on the transmission distance.) Certain network embodimentsprovide for a high bandwidth by laying out several networks in parallel,e.g., and in low-level metals. Certain network embodiments communicatein low-level metals and over short distances, and thus are very powerefficient.

Certain embodiments of networks include architectural support for flowcontrol. For example, in spatial accelerators composed of smallprocessing elements (PEs), communications latency and bandwidth may becritical to overall program performance. Certain embodiments hereinprovide for a light-weight, circuit switched network which facilitatescommunication between PEs in spatial processing arrays, such as thespatial array shown in FIG. 6, and the micro-architectural controlfeatures necessary to support this network. Certain embodiments of anetwork enable the construction of point-to-point, flow controlledcommunications channels which support the communications of the datafloworiented processing elements (PEs). In addition to point-to-pointcommunications, certain networks herein also support multicastcommunications. Communications channels may be formed by staticallyconfiguring the network to from virtual circuits between PEs. Circuitswitching techniques herein may decrease communications latency andcommensurately minimize network buffering, e.g., resulting in both highperformance and high energy efficiency. In certain embodiments of anetwork, inter-PE latency may be as low as a zero cycles, meaning thatthe downstream PE may operate on data in the cycle after it is produced.To obtain even higher bandwidth, and to admit more programs, multiplenetworks may be laid out in parallel, e.g., as shown in FIG. 6.

Spatial architectures, such as the one shown in FIG. 6, may be thecomposition of lightweight processing elements connected by an inter-PEnetwork (and/or communications network (e.g., a network dataflowendpoint circuit thereof)). Programs, viewed as dataflow graphs, may bemapped onto the architecture by configuring PEs and the network.Generally, PEs may be configured as dataflow operators, and once (e.g.,all) input operands arrive at the PE, some operation may then occur, andthe result are forwarded to the desired downstream PEs. PEs maycommunicate over dedicated virtual circuits which are formed bystatically configuring a circuit switched communications network. Thesevirtual circuits may be flow controlled and fully back-pressured, e.g.,such that PEs will stall if either the source has no data or thedestination is full. At runtime, data may flow through the PEsimplementing the mapped algorithm. For example, data may be streamed infrom memory, through the fabric, and then back out to memory.Embodiments of this architecture may achieve remarkable performanceefficiency relative to traditional multicore processors: for example,where compute, in the form of PEs, is simpler and more numerous thanlarger cores and communication are direct, e.g., as opposed to anextension of the memory system.

FIG. 6 illustrates an accelerator tile 600 comprising an array ofprocessing elements (PEs) according to embodiments of the disclosure.The interconnect network is depicted as circuit switched, staticallyconfigured communications channels. For example, a set of channelscoupled together by a switch (e.g., switch 610 in a first network andswitch 611 in a second network). The first network and second networkmay be separate or coupled together. For example, switch 610 may coupleone or more of the four data paths (612, 614, 616, 618) together, e.g.,as configured to perform an operation according to a dataflow graph. Inone embodiment, the number of data paths is any plurality. Processingelement (e.g., processing element 604) may be as disclosed herein, forexample, as in FIG. 9. Accelerator tile 600 includes a memory/cachehierarchy interface 602, e.g., to interface the accelerator tile 600with a memory and/or cache. A data path (e.g., 618) may extend toanother tile or terminate, e.g., at the edge of a tile. A processingelement may include an input buffer (e.g., buffer 606) and an outputbuffer (e.g., buffer 608).

Operations may be executed based on the availability of their inputs andthe status of the PE. A PE may obtain operands from input channels andwrite results to output channels, although internal register state mayalso be used. Certain embodiments herein include a configurabledataflow-friendly PE. FIG. 9 shows a detailed block diagram of one suchPE: the integer PE. This PE consists of several I/O buffers, an ALU, astorage register, some instruction registers, and a scheduler. Eachcycle, the scheduler may select an instruction for execution based onthe availability of the input and output buffers and the status of thePE. The result of the operation may then be written to either an outputbuffer or to a (e.g., local to the PE) register. Data written to anoutput buffer may be transported to a downstream PE for furtherprocessing. This style of PE may be extremely energy efficient, forexample, rather than reading data from a complex, multi-ported registerfile, a PE reads the data from a register. Similarly, instructions maybe stored directly in a register, rather than in a virtualizedinstruction cache.

Instruction registers may be set during a special configuration step.During this step, auxiliary control wires and state, in addition to theinter-PE network, may be used to stream in configuration across theseveral PEs comprising the fabric. As result of parallelism, certainembodiments of such a network may provide for rapid reconfiguration,e.g., a tile sized fabric may be configured in less than about 10microseconds.

FIG. 9 represents one example configuration of a processing element,e.g., in which all architectural elements are minimally sized. In otherembodiments, each of the components of a processing element isindependently scaled to produce new PEs. For example, to handle morecomplicated programs, a larger number of instructions that areexecutable by a PE may be introduced. A second dimension ofconfigurability is in the function of the PE arithmetic logic unit(ALU). In FIG. 9, an integer PE is depicted which may support addition,subtraction, and various logic operations. Other kinds of PEs may becreated by substituting different kinds of functional units into the PE.An integer multiplication PE, for example, might have no registers, asingle instruction, and a single output buffer. Certain embodiments of aPE decompose a fused multiply add (FMA) into separate, but tightlycoupled floating multiply and floating add units to improve support formultiply-add-heavy workloads. PEs are discussed further below.

FIG. 7A illustrates a configurable data path network 700 (e.g., ofnetwork one or network two discussed in reference to FIG. 6) accordingto embodiments of the disclosure. Network 700 includes a plurality ofmultiplexers (e.g., multiplexers 702, 704, 706) that may be configured(e.g., via their respective control signals) to connect one or more datapaths (e.g., from PEs) together. FIG. 7B illustrates a configurable flowcontrol path network 701 (e.g., network one or network two discussed inreference to FIG. 6) according to embodiments of the disclosure. Anetwork may be a light-weight PE-to-PE network. Certain embodiments of anetwork may be thought of as a set of composable primitives for theconstruction of distributed, point-to-point data channels. FIG. 7A showsa network that has two channels enabled, the bold black line and thedotted black line. The bold black line channel is multicast, e.g., asingle input is sent to two outputs. Note that channels may cross atsome points within a single network, even though dedicated circuitswitched paths are formed between channel endpoints. Furthermore, thiscrossing may not introduce a structural hazard between the two channels,so that each operates independently and at full bandwidth.

Implementing distributed data channels may include two paths,illustrated in FIGS. 7A-7B. The forward, or data path, carries data froma producer to a consumer. Multiplexors may be configured to steer dataand valid bits from the producer to the consumer, e.g., as in FIG. 7A.In the case of multicast, the data will be steered to multiple consumerendpoints. The second portion of this embodiment of a network is theflow control or backpressure path, which flows in reverse of the forwarddata path, e.g., as in FIG. 7B. Consumer endpoints may assert when theyare ready to accept new data. These signals may then be steered back tothe producer using configurable logical conjunctions, labelled as (e.g.,backflow) flowcontrol function in FIG. 7B. In one embodiment, eachflowcontrol function circuit may be a plurality of switches (e.g.,muxes), for example, similar to FIG. 7A. The flow control path mayhandle returning control data from consumer to producer. Conjunctionsmay enable multicast, e.g., where each consumer is ready to receive databefore the producer assumes that it has been received. In oneembodiment, a PE is a PE that has a dataflow operator as itsarchitectural interface. Additionally or alternatively, in oneembodiment a PE may be any kind of PE (e.g., in the fabric), forexample, but not limited to, a PE that has an instruction pointer,triggered instruction, or state machine based architectural interface.

The network may be statically configured, e.g., in addition to PEs beingstatically configured. During the configuration step, configuration bitsmay be set at each network component. These bits control, for example,the multiplexer selections and flow control functions. A network maycomprise a plurality of networks, e.g., a data path network and a flowcontrol path network. A network or plurality of networks may utilizepaths of different widths (e.g., a first width, and a narrower or widerwidth). In one embodiment, a data path network has a wider (e.g., bittransport) width than the width of a flow control path network. In oneembodiment, each of a first network and a second network includes theirown data path network and flow control path network, e.g., data pathnetwork A and flow control path network A and wider data path network Band flow control path network B.

Certain embodiments of a network are bufferless, and data is to movebetween producer and consumer in a single cycle. Certain embodiments ofa network are also boundless, that is, the network spans the entirefabric. In one embodiment, one PE is to communicate with any other PE ina single cycle. In one embodiment, to improve routing bandwidth, severalnetworks may be laid out in parallel between rows of PEs.

Relative to FPGAs, certain embodiments of networks herein have threeadvantages: area, frequency, and program expression. Certain embodimentsof networks herein operate at a coarse grain, e.g., which reduces thenumber configuration bits, and thereby the area of the network. Certainembodiments of networks also obtain area reduction by implementing flowcontrol logic directly in circuitry (e.g., silicon). Certain embodimentsof hardened network implementations also enjoys a frequency advantageover FPGA. Because of an area and frequency advantage, a power advantagemay exist where a lower voltage is used at throughput parity. Finally,certain embodiments of networks provide better high-level semantics thanFPGA wires, especially with respect to variable timing, and thus thosecertain embodiments are more easily targeted by compilers. Certainembodiments of networks herein may be thought of as a set of composableprimitives for the construction of distributed, point-to-point datachannels.

In certain embodiments, a multicast source may not assert its data validunless it receives a ready signal from each sink. Therefore, an extraconjunction and control bit may be utilized in the multicast case.

Like certain PEs, the network may be statically configured. During thisstep, configuration bits are set at each network component. These bitscontrol, for example, the multiplexer selection and flow controlfunction. The forward path of our network requires some bits to swingits muxes. In the example shown in FIG. 7A, four bits per hop arerequired: the east and west muxes utilize one bit each, while thesouthbound multiplexer utilize two bits. In this embodiment, four bitsmay be utilized for the data path, but 7 bits may be utilized for theflow control function (e.g., in the flow control path network). Otherembodiments may utilize more bits, for example, if a CSA furtherutilizes a north-south direction. The flow control function may utilizea control bit for each direction from which flow control can come. Thismay enables the setting of the sensitivity of the flow control functionstatically. The table 1 below summarizes the Boolean algebraicimplementation of the flow control function for the network in FIG. 7B,with configuration bits capitalized. In this example, seven bits areutilized.

TABLE 1 Flow Implementation readyToEast (EAST_WEST_SENSITIVE +readyFromWest) * (EAST_SOUTH_SENSITIVE + readyFromSouth) readyToWest(WEST_EAST_SENSITIVE + readyFromEast) * (WEST_SOUTH_SENSITIVE +readyFromSouth) readyToNorth (NORTH_WEST_SENSITIVE + readyFromWest) *(NORTH_EAST_SENSITIVE + readyFromEast) * (NORTH_SOUTH_SENSITIVE +readyFromSouth)For the third flow control box from the left in FIG. 7B,EAST_WEST_SENSITIVE and NORTH_SOUTH_SENSITIVE are depicted as set toimplement the flow control for the bold line and dotted line channels,respectively.

FIG. 8 illustrates a hardware processor tile 800 comprising anaccelerator 802 according to embodiments of the disclosure. Accelerator802 may be a CSA according to this disclosure. Tile 800 includes aplurality of cache banks (e.g., cache bank 808). Request address file(RAF) circuits 810 may be included, e.g., as discussed below in Section2.2. ODI may refer to an On Die Interconnect, e.g., an interconnectstretching across an entire die connecting up all the tiles. OTI mayrefer to an On Tile Interconnect, for example, stretching across a tile,e.g., connecting cache banks on the tile together.

2.1 Processing Elements

In certain embodiments, a CSA includes an array of heterogeneous PEs, inwhich the fabric is composed of several types of PEs each of whichimplement only a subset of the dataflow operators. By way of example,FIG. 9 shows a provisional implementation of a PE capable ofimplementing a broad set of the integer and control operations. OtherPEs, including those supporting floating point addition, floating pointmultiplication, buffering, and certain control operations may have asimilar implementation style, e.g., with the appropriate (dataflowoperator) circuitry substituted for the ALU. PEs (e.g., dataflowoperators) of a CSA may be configured (e.g., programmed) before thebeginning of execution to implement a particular dataflow operation fromamong the set that the PE supports. A configuration may include one ortwo control words which specify an opcode controlling the ALU, steer thevarious multiplexors within the PE, and actuate dataflow into and out ofthe PE channels. Dataflow operators may be implemented by microcodingthese configurations bits. The depicted integer PE 900 in FIG. 9 isorganized as a single-stage logical pipeline flowing from top to bottom.Data enters PE 900 from one of set of local networks, where it isregistered in an input buffer for subsequent operation. Each PE maysupport a number of wide, data-oriented and narrow, control-orientedchannels. The number of provisioned channels may vary based on PEfunctionality, but one embodiment of an integer-oriented PE has 2 wideand 1-2 narrow input and output channels. Although the integer PE isimplemented as a single-cycle pipeline, other pipelining choices may beutilized. For example, multiplication PEs may have multiple pipelinestages.

PE execution may proceed in a dataflow style. Based on the configurationmicrocode, the scheduler (e.g., or an operations manager circuit) mayexamine the status of the PE ingress and egress buffers, and, when allthe inputs for the configured operation have arrived and the egressbuffer of the operation is available, orchestrates the actual executionof the operation by a dataflow operator (e.g., on the ALU). Theresulting value may be placed in the configured egress buffer. Transfersbetween the egress buffer of one PE and the ingress buffer of another PEmay occur asynchronously as buffering becomes available. In certainembodiments, PEs are provisioned such that at least one dataflowoperation completes per cycle. Section 2 discussed dataflow operatorencompassing primitive operations, such as add, xor, or pick. Certainembodiments may provide advantages in energy, area, performance, andlatency. In one embodiment, with an extension to a PE control path, morefused combinations may be enabled. In one embodiment, the width of theprocessing elements is 64 bits, e.g., for the heavy utilization ofdouble-precision floating point computation in HPC and to support 64-bitmemory addressing.

2.2 Communications Networks

Embodiments of the CSA microarchitecture provide a hierarchy of networkswhich together provide an implementation of the architecturalabstraction of latency-insensitive channels across multiplecommunications scales. The lowest level of CSA communications hierarchymay be the local network. The local network may be statically circuitswitched, e.g., using configuration registers to swing multiplexor(s) inthe local network data-path to form fixed electrical paths betweencommunicating PEs. In one embodiment, the configuration of the localnetwork is set once per dataflow graph, e.g., at the same time as the PEconfiguration. In one embodiment, static, circuit switching optimizesfor energy, e.g., where a large majority (perhaps greater than 95%) ofCSA communications traffic will cross the local network. A program mayinclude terms which are used in multiple expressions. To optimize forthis case, embodiments herein provide for hardware support for multicastwithin the local network. Several local networks may be ganged togetherto form routing channels, e.g., which are interspersed (as a grid)between rows and columns of PEs. As an optimization, several localnetworks may be included to carry control tokens. In comparison to aFPGA interconnect, a CSA local network may be routed at the granularityof the data-path, and another difference may be a CSA's treatment ofcontrol. One embodiment of a CSA local network is explicitly flowcontrolled (e.g., back-pressured). For example, for each forwarddata-path and multiplexor set, a CSA is to provide a backward-flowingflow control path that is physically paired with the forward data-path.The combination of the two microarchitectural paths may provide alow-latency, low-energy, low-area, point-to-point implementation of thelatency-insensitive channel abstraction. In one embodiment, a CSA's flowcontrol lines are not visible to the user program, but they may bemanipulated by the architecture in service of the user program. Forexample, the exception handling mechanisms described in Section 1.2 maybe achieved by pulling flow control lines to a “not present” state uponthe detection of an exceptional condition. This action may not onlygracefully stalls those parts of the pipeline which are involved in theoffending computation, but may also preserve the machine state leadingup the exception, e.g., for diagnostic analysis. The second networklayer, e.g., the mezzanine network, may be a shared, packet switchednetwork. Mezzanine network may include a plurality of distributednetwork controllers, network dataflow endpoint circuits. The mezzaninenetwork (e.g., the network schematically indicated by the dotted box inFIG. 49) may provide more general, long range communications, e.g., atthe cost of latency, bandwidth, and energy. In some programs, mostcommunications may occur on the local network, and thus mezzaninenetwork provisioning will be considerably reduced in comparison, forexample, each PE may connects to multiple local networks, but the CSAwill provision only one mezzanine endpoint per logical neighborhood ofPEs. Since the mezzanine is effectively a shared network, each mezzaninenetwork may carry multiple logically independent channels, e.g., and beprovisioned with multiple virtual channels. In one embodiment, the mainfunction of the mezzanine network is to provide wide-rangecommunications in-between PEs and between PEs and memory. In addition tothis capability, the mezzanine may also include network dataflowendpoint circuit(s), for example, to perform certain dataflowoperations. In addition to this capability, the mezzanine may alsooperate as a runtime support network, e.g., by which various servicesmay access the complete fabric in a user-program-transparent manner. Inthis capacity, the mezzanine endpoint may function as a controller forits local neighborhood, for example, during CSA configuration. To formchannels spanning a CSA tile, three subchannels and two local networkchannels (which carry traffic to and from a single channel in themezzanine network) may be utilized. In one embodiment, one mezzaninechannel is utilized, e.g., one mezzanine and two local=3 total networkhops.

The composability of channels across network layers may be extended tohigher-level network layers at the inter-tile, inter-die, and fabricgranularities.

FIG. 9 illustrates a processing element 900 according to embodiments ofthe disclosure. In one embodiment, operation configuration register 919is loaded during configuration (e.g., mapping) and specifies theparticular operation (or operations) this processing (e.g., compute)element is to perform. Register 920 activity may be controlled by thatoperation (an output of multiplexer 916, e.g., controlled by thescheduler 914). Scheduler 914 may schedule an operation or operations ofprocessing element 900, for example, when input data and control inputarrives. Control input buffer 922 is connected to local network 902(e.g., and local network 902 may include a data path network as in FIG.7A and a flow control path network as in FIG. 7B) and is loaded with avalue when it arrives (e.g., the network has a data bit(s) and validbit(s)). Control output buffer 932, data output buffer 934, and/or dataoutput buffer 936 may receive an output of processing element 900, e.g.,as controlled by the operation (an output of multiplexer 916). Statusregister 938 may be loaded whenever the ALU 918 executes (alsocontrolled by output of multiplexer 916). Data in control input buffer922 and control output buffer 932 may be a single bit. Multiplexer 921(e.g., operand A) and multiplexer 923 (e.g., operand B) may sourceinputs.

For example, suppose the operation of this processing (e.g., compute)element is (or includes) what is called call a pick in FIG. 3B. Theprocessing element 900 then is to select data from either data inputbuffer 924 or data input buffer 926, e.g., to go to data output buffer934 (e.g., default) or data output buffer 936. The control bit in 922may thus indicate a 0 if selecting from data input buffer 924 or a 1 ifselecting from data input buffer 926.

For example, suppose the operation of this processing (e.g., compute)element is (or includes) what is called call a switch in FIG. 3B. Theprocessing element 900 is to output data to data output buffer 934 ordata output buffer 936, e.g., from data input buffer 924 (e.g., default)or data input buffer 926. The control bit in 922 may thus indicate a 0if outputting to data output buffer 934 or a 1 if outputting to dataoutput buffer 936.

Multiple networks (e.g., interconnects) may be connected to a processingelement, e.g., (input) networks 902, 904, 906 and (output) networks 908,910, 912. The connections may be switches, e.g., as discussed inreference to FIGS. 7A and 7B. In one embodiment, each network includestwo sub-networks (or two channels on the network), e.g., one for thedata path network in FIG. 7A and one for the flow control (e.g.,backpressure) path network in FIG. 7B. As one example, local network 902(e.g., set up as a control interconnect) is depicted as being switched(e.g., connected) to control input buffer 922. In this embodiment, adata path (e.g., network as in FIG. 7A) may carry the control inputvalue (e.g., bit or bits) (e.g., a control token) and the flow controlpath (e.g., network) may carry the backpressure signal (e.g.,backpressure or no-backpressure token) from control input buffer 922,e.g., to indicate to the upstream producer (e.g., PE) that a new controlinput value is not to be loaded into (e.g., sent to) control inputbuffer 922 until the backpressure signal indicates there is room in thecontrol input buffer 922 for the new control input value (e.g., from acontrol output buffer of the upstream producer). In one embodiment, thenew control input value may not enter control input buffer 922 untilboth (i) the upstream producer receives the “space available”backpressure signal from “control input” buffer 922 and (ii) the newcontrol input value is sent from the upstream producer, e.g., and thismay stall the processing element 900 until that happens (and space inthe target, output buffer(s) is available).

Data input buffer 924 and data input buffer 926 may perform similarly,e.g., local network 904 (e.g., set up as a data (as opposed to control)interconnect) is depicted as being switched (e.g., connected) to datainput buffer 924. In this embodiment, a data path (e.g., network as inFIG. 7A) may carry the data input value (e.g., bit or bits) (e.g., adataflow token) and the flow control path (e.g., network) may carry thebackpressure signal (e.g., backpressure or no-backpressure token) fromdata input buffer 924, e.g., to indicate to the upstream producer (e.g.,PE) that a new data input value is not to be loaded into (e.g., sent to)data input buffer 924 until the backpressure signal indicates there isroom in the data input buffer 924 for the new data input value (e.g.,from a data output buffer of the upstream producer). In one embodiment,the new data input value may not enter data input buffer 924 until both(i) the upstream producer receives the “space available” backpressuresignal from “data input” buffer 924 and (ii) the new data input value issent from the upstream producer, e.g., and this may stall the processingelement 900 until that happens (and space in the target, outputbuffer(s) is available). A control output value and/or data output valuemay be stalled in their respective output buffers (e.g., 932, 934, 936)until a backpressure signal indicates there is available space in theinput buffer for the downstream processing element(s).

A processing element 900 may be stalled from execution until itsoperands (e.g., a control input value and its corresponding data inputvalue or values) are received and/or until there is room in the outputbuffer(s) of the processing element 900 for the data that is to beproduced by the execution of the operation on those operands.

2.3 Memory Interface

The request address file (RAF) circuit, a simplified version of which isshown in FIG. 10, may be responsible for executing memory operations andserves as an intermediary between the CSA fabric and the memoryhierarchy. As such, the main microarchitectural task of the RAF may beto rationalize the out-of-order memory subsystem with the in-ordersemantics of CSA fabric. In this capacity, the RAF circuit may beprovisioned with completion buffers, e.g., queue-like structures thatre-order memory responses and return them to the fabric in the requestorder. The second major functionality of the RAF circuit may be toprovide support in the form of address translation and a page walker.Incoming virtual addresses may be translated to physical addresses usinga channel-associative translation lookaside buffer (TLB). To provideample memory bandwidth, each CSA tile may include multiple RAF circuits.Like the various PEs of the fabric, the RAF circuits may operate in adataflow-style by checking for the availability of input arguments andoutput buffering, if required, before selecting a memory operation toexecute. Unlike some PEs, however, the RAF circuit is multiplexed amongseveral co-located memory operations. A multiplexed RAF circuit may beused to minimize the area overhead of its various subcomponents, e.g.,to share the Accelerator Cache Interface (ACI) network (described inmore detail in Section 2.4), shared virtual memory (SVM) supporthardware, mezzanine network interface, and other hardware managementfacilities. However, there are some program characteristics that mayalso motivate this choice. In one embodiment, a (e.g., valid) dataflowgraph is to poll memory in a shared virtual memory system.Memory-latency-bound programs, like graph traversals, may utilize manyseparate memory operations to saturate memory bandwidth due tomemory-dependent control flow. Although each RAF may be multiplexed, aCSA may include multiple (e.g., between 8 and 32) RAFs at a tilegranularity to ensure adequate cache bandwidth. RAFs may communicatewith the rest of the fabric via both the local network and the mezzaninenetwork. Where RAFs are multiplexed, each RAF may be provisioned withseveral ports into the local network. These ports may serve as aminimum-latency, highly-deterministic path to memory for use bylatency-sensitive or high-bandwidth memory operations. In addition, aRAF may be provisioned with a mezzanine network endpoint, e.g., whichprovides memory access to runtime services and distant user-level memoryaccessors.

FIG. 10 illustrates a request address file (RAF) circuit 1000 accordingto embodiments of the disclosure. In one embodiment, at configurationtime, the memory load and store operations that were in a dataflow graphare specified in registers 1010. The arcs to those memory operations inthe dataflow graphs may then be connected to the input queues 1022,1024, and 1026. The arcs from those memory operations are thus to leavecompletion buffers 1028, 1030, or 1032. Dependency tokens (which may besingle bits) arrive into queues 1018 and 1020. Dependency tokens are toleave from queue 1016. Dependency token counter 1014 may be a compactrepresentation of a queue and track a number of dependency tokens usedfor any given input queue. If the dependency token counters 1014saturate, no additional dependency tokens may be generated for newmemory operations. Accordingly, a memory ordering circuit (e.g., a RAFin FIG. 11) may stall scheduling new memory operations until thedependency token counters 1014 becomes unsaturated.

As an example for a load, an address arrives into queue 1022 which thescheduler 1012 matches up with a load in 1010. A completion buffer slotfor this load is assigned in the order the address arrived. Assumingthis particular load in the graph has no dependencies specified, theaddress and completion buffer slot are sent off to the memory system bythe scheduler (e.g., via memory command 1042). When the result returnsto multiplexer 1040 (shown schematically), it is stored into thecompletion buffer slot it specifies (e.g., as it carried the target slotall along though the memory system). The completion buffer sends resultsback into local network (e.g., local network 1002, 1004, 1006, or 1008)in the order the addresses arrived.

Stores may be similar except both address and data have to arrive beforeany operation is sent off to the memory system.

2.4 Cache

Dataflow graphs may be capable of generating a profusion of (e.g., wordgranularity) requests in parallel. Thus, certain embodiments of the CSAprovide a cache subsystem with sufficient bandwidth to service the CSA.A heavily banked cache microarchitecture, e.g., as shown in FIG. 11 maybe utilized. FIG. 11 illustrates a circuit 1100 with a plurality ofrequest address file (RAF) circuits (e.g., RAF circuit (1)) coupledbetween a plurality of accelerator tiles (1108, 1110, 1112, 1114) and aplurality of cache banks (e.g., cache bank 1102) according toembodiments of the disclosure. In one embodiment, the number of RAFs andcache banks may be in a ratio of either 1:1 or 1:2. Cache banks maycontain full cache lines (e.g., as opposed to sharding by word), witheach line having exactly one home in the cache. Cache lines may bemapped to cache banks via a pseudo-random function. The CSA may adoptthe shared virtual memory (SVM) model to integrate with other tiledarchitectures. Certain embodiments include an Accelerator CacheInterface (ACI) network connecting the RAFs to the cache banks. Thisnetwork may carry address and data between the RAFs and the cache. Thetopology of the ACI may be a cascaded crossbar, e.g., as a compromisebetween latency and implementation complexity.

2.5 Network Resources, e.g., Circuitry, to Perform (e.g., Dataflow)Operations

In certain embodiments, processing elements (PEs) communicate usingdedicated virtual circuits which are formed by statically configuring a(e.g., circuit switched) communications network. These virtual circuitsmay be flow controlled and fully back-pressured, e.g., such that a PEwill stall if either the source has no data or its destination is full.At runtime, data may flow through the PEs implementing the mappeddataflow graph (e.g., mapped algorithm). For example, data may bestreamed in from memory, through the (e.g., fabric area of a) spatialarray of processing elements, and then back out to memory.

Such an architecture may achieve remarkable performance efficiencyrelative to traditional multicore processors: compute, e.g., in the formof PEs, may be simpler and more numerous than cores and communicationsmay be direct, e.g., as opposed to an extension of the memory system.However, the (e.g., fabric area of) spatial array of processing elementsmay be tuned for the implementation of compiler-generated expressiontrees, which may feature little multiplexing or demultiplexing. Certainembodiments herein extend (for example, via network resources, such as,but not limited to, network dataflow endpoint circuits) the architectureto support (e.g., high-radix) multiplexing and/or demultiplexing, forexample, especially in the context of function calls.

Spatial arrays, such as the spatial array of processing elements 101 inFIG. 1, may use (e.g., packet switched) networks for communications.Certain embodiments herein provide circuitry to overlay high-radixdataflow operations on these networks for communications. For example,certain embodiments herein utilize the existing network forcommunications (e.g., interconnect network 104 described in reference toFIG. 1) to provide data routing capabilities between processing elementsand other components of the spatial array, but also augment the network(e.g., network endpoints) to support the performance and/or control ofsome (e.g., less than all) of dataflow operations (e.g., withoututilizing the processing elements to perform those dataflow operations).In one embodiment, (e.g., high radix) dataflow operations are supportedwith special hardware structures (e.g. network dataflow endpointcircuits) within a spatial array, for example, without consumingprocessing resources or degrading performance (e.g., of the processingelements).

In one embodiment, a circuit switched network between two points (e.g.,between a producer and consumer of data) includes a dedicatedcommunication line between those two points, for example, with (e.g.,physical) switches between the two points set to create a (e.g.,exclusive) physical circuit between the two points. In one embodiment, acircuit switched network between two points is set up at the beginningof use of the connection between the two points and maintainedthroughout the use of the connection. In another embodiment, a packetswitched network includes a shared communication line (e.g., channel)between two (e.g., or more) points, for example, where packets fromdifferent connections share that communication line (for example, routedaccording to data of each packet, e.g., in the header of a packetincluding a header and a payload). An example of a packet switchednetwork is discussed below, e.g., in reference to a mezzanine network.

FIG. 12 illustrates a data flow graph 1200 of a pseudocode function call1201 according to embodiments of the disclosure. Function call 1201 isto load two input data operands (e.g., indicated by pointers *a and *b,respectively), and multiply them together, and return the resultantdata. This or other functions may be performed multiple times (e.g., ina dataflow graph). The dataflow graph in FIG. 12 illustrates a PickAnydataflow operator 1202 to perform the operation of selecting a controldata (e.g., an index) (for example, from call sites 1202A) and copyingwith copy dataflow operator 1204 that control data (e.g., index) to eachof the first Pick dataflow operator 1206, second Pick dataflow operator1206, and Switch dataflow operator 1216. In one embodiment, an index(e.g., from the PickAny thus inputs and outputs data to the same indexposition, e.g., of [0, 1 . . . M], where M is an integer. First Pickdataflow operator 1206 may then pull one input data element of aplurality of input data elements 1206A according to the control data,and use the one input data element as (*a) to then load the input datavalue stored at *a with load dataflow operator 1210. Second Pickdataflow operator 1208 may then pull one input data element of aplurality of input data elements 1208A according to the control data,and use the one input data element as (*b) to then load the input datavalue stored at *b with load dataflow operator 1212. Those two inputdata values may then be multiplied by multiplication dataflow operator1214 (e.g., as a part of a processing element). The resultant data ofthe multiplication may then be routed (e.g., to a downstream processingelement or other component) by Switch dataflow operator 1216, e.g., tocall sites 1216A, for example, according to the control data (e.g.,index) to Switch dataflow operator 1216.

FIG. 12 is an example of a function call where the number of dataflowoperators used to manage the steering of data (e.g., tokens) may besignificant, for example, to steer the data to and/or from call sites.In one example, one or more of PickAny dataflow operator 1202, firstPick dataflow operator 1206, second Pick dataflow operator 1206, andSwitch dataflow operator 1216 may be utilized to route (e.g., steer)data, for example, when there are multiple (e.g., many) call sites. Inan embodiment where a (e.g., main) goal of introducing a multiplexedand/or demultiplexed function call is to reduce the implementation areaof a particular dataflow graph, certain embodiments herein (e.g., ofmicroarchitecture) reduce the area overhead of such multiplexed and/ordemultiplexed (e.g., portions) of dataflow graphs.

FIG. 13 illustrates a spatial array 1301 of processing elements (PEs)with a plurality of network dataflow endpoint circuits (1302, 1304,1306) according to embodiments of the disclosure. Spatial array 1301 ofprocessing elements may include a communications (e.g., interconnect)network in between components, for example, as discussed herein. In oneembodiment, communications network is one or more (e.g., channels of a)packet switched communications network. In one embodiment,communications network is one or more circuit switched, staticallyconfigured communications channels. For example, a set of channelscoupled together by a switch (e.g., switch 1310 in a first network andswitch 1311 in a second network). The first network and second networkmay be separate or coupled together. For example, switch 1310 may coupleone or more of a plurality (e.g., four) data paths therein together,e.g., as configured to perform an operation according to a dataflowgraph. In one embodiment, the number of data paths is any plurality.Processing element (e.g., processing element 1308) may be as disclosedherein, for example, as in FIG. 9. Accelerator tile 1300 includes amemory/cache hierarchy interface 1312, e.g., to interface theaccelerator tile 1300 with a memory and/or cache. A data path may extendto another tile or terminate, e.g., at the edge of a tile. A processingelement may include an input buffer (e.g., buffer 1309) and an outputbuffer.

Operations may be executed based on the availability of their inputs andthe status of the PE. A PE may obtain operands from input channels andwrite results to output channels, although internal register state mayalso be used. Certain embodiments herein include a configurabledataflow-friendly PE. FIG. 9 shows a detailed block diagram of one suchPE: the integer PE. This PE consists of several I/O buffers, an ALU, astorage register, some instruction registers, and a scheduler. Eachcycle, the scheduler may select an instruction for execution based onthe availability of the input and output buffers and the status of thePE. The result of the operation may then be written to either an outputbuffer or to a (e.g., local to the PE) register. Data written to anoutput buffer may be transported to a downstream PE for furtherprocessing. This style of PE may be extremely energy efficient, forexample, rather than reading data from a complex, multi-ported registerfile, a PE reads the data from a register. Similarly, instructions maybe stored directly in a register, rather than in a virtualizedinstruction cache.

Instruction registers may be set during a special configuration step.During this step, auxiliary control wires and state, in addition to theinter-PE network, may be used to stream in configuration across theseveral PEs comprising the fabric. As result of parallelism, certainembodiments of such a network may provide for rapid reconfiguration,e.g., a tile sized fabric may be configured in less than about 10microseconds.

Certain embodiments herein overlay (e.g., high-radix) dataflowoperations on a communications network, e.g., in addition to thecommunications network's routing of data between the processingelements, memory, etc. and/or the communications network performingother communications (e.g., not data processing) operations. Certainembodiments herein are directed to a communications network (e.g., apacket switched network) of a (e.g., coupled to) spatial array ofprocessing elements (e.g., a CSA) to perform certain dataflowoperations, e.g., in addition to the communications network routing databetween the processing elements, memory, etc. or the communicationsnetwork performing other communications operations. Certain embodimentsherein are directed to network dataflow endpoint circuits that (e.g.,each) perform (e.g., a portion or all) a dataflow operation oroperations, for example, a pick or switch dataflow operation, e.g., of adataflow graph. Certain embodiments herein include augmented networkendpoints (e.g., network dataflow endpoint circuits) to support thecontrol for (e.g., a plurality of or a subset of) dataflow operation(s),e.g., utilizing the network endpoints to perform a (e.g., dataflow)operation instead of a processing element (e.g., core) orarithmetic-logic unit (e.g. to perform arithmetic and logic operations)performing that (e.g., dataflow) operation. In one embodiment, a networkdataflow endpoint circuit is separate from a spatial array (e.g. aninterconnect or fabric thereof) and/or processing elements.

Further, depicted accelerator tile 1300 includes packet switchedcommunications network 1314, for example, as part of a mezzaninenetwork, e.g., as described below. Certain embodiments herein allow for(e.g., a distributed) dataflow operations (e.g., operations that onlyroute data) to be performed on (e.g., within) the communications network(e.g., and not in the processing element(s)). As an example, adistributed Pick dataflow operation of a dataflow graph is depicted inFIG. 13. Particularly, distributed pick is implemented using threeseparate configurations on three separate network (e.g., global)endpoints (e.g., network dataflow endpoint circuits (1302, 1304, 1306)).Dataflow operations may be distributed, e.g., with several endpoints tobe configured in a coordinated manner. For example, a compilation toolmay understand the need for coordination. Endpoints (e.g., networkdataflow endpoint circuits) may be shared among several distributedoperations, for example, a dataflow operation (e.g., pick) endpoint maybe collated with several sends related to the dataflow operation (e.g.,pick). A distributed dataflow operation (e.g., pick) may generate thesame result the same as a non-distributed dataflow operation (e.g.,pick). In certain embodiment, a difference between distributed andnon-distributed dataflow operations is that in the distributed dataflowoperations have their data (e.g., data to be routed, but which may notinclude control data) over a packet switched communications network,e.g., with associated flow control and distributed coordination.Although different sized processing elements (PE) are shown, in oneembodiment, each processing element is of the same size (e.g., siliconarea). In one embodiment, a buffer element to buffer data may also beincluded, e.g., separate from a processing element.

As one example, a pick dataflow operation may have a plurality of inputsand steer (e.g., route) one of them as an output, e.g., as in FIG. 12.Instead of utilizing a processing element to perform the pick dataflowoperation, it may be achieved with one or more of network communicationresources (e.g., network dataflow endpoint circuits). Additionally oralternatively, the network dataflow endpoint circuits may route databetween processing elements, e.g., for the processing elements toperform processing operations on the data. Embodiments herein may thusutilize to the communications network to perform (e.g., steering)dataflow operations. Additionally or alternatively, the network dataflowendpoint circuits may perform as a mezzanine network discussed below.

In the depicted embodiment, packet switched communications network 1314may handle certain (e.g., configuration) communications, for example, toprogram the processing elements and/or circuit switched network (e.g.,network 1313, which may include switches). In one embodiment, a circuitswitched network is configured (e.g., programmed) to perform one or moreoperations (e.g., dataflow operations of a dataflow graph).

Packet switched communications network 1314 includes a plurality ofendpoints (e.g., network dataflow endpoint circuits (1302, 1304, 1306).In one embodiment, each endpoint includes an address or other indicatorvalue to allow data to be routed to and/or from that endpoint, e.g.,according to (e.g., a header of) a data packet.

Additionally or alternatively to performing one or more of the above,packet switched communications network 1314 may perform dataflowoperations. Network dataflow endpoint circuits (1302, 1304, 1306) may beconfigured (e.g., programmed) to perform a (e.g., distributed pick)operation of a dataflow graph. Programming of components (e.g., acircuit) are described herein. An embodiment of configuring a networkdataflow endpoint circuit (e.g., an operation configuration registerthereof) is discussed in reference to FIG. 14.

As an example of a distributed pick dataflow operation, network dataflowendpoint circuits (1302, 1304, 1306) in FIG. 13 may be configured (e.g.,programmed) to perform a distributed pick operation of a dataflow graph.An embodiment of configuring a network dataflow endpoint circuit (e.g.,an operation configuration register thereof) is discussed in referenceto FIG. 14. Additionally or alternatively to configuring remote endpointcircuits, local endpoint circuits may also be configured according tothis disclosure.

Network dataflow endpoint circuit 1302 may be configured to receiveinput data from a plurality of sources (e.g., network dataflow endpointcircuit 1304 and network dataflow endpoint circuit 1306), and to outputresultant data, e.g., as in FIG. 12), for example, according to controldata. Network dataflow endpoint circuit 1304 may be configured toprovide (e.g., send) input data to network dataflow endpoint circuit1302, e.g., on receipt of the input data from processing element 1322.This may be referred to as Input 0 in FIG. 13. In one embodiment,circuit switched network is configured (e.g., programmed) to provide adedicated communication line between processing element 1322 and networkdataflow endpoint circuit 1304 along path 1324. Network dataflowendpoint circuit 1306 may be configured to provide (e.g., send) inputdata to network dataflow endpoint circuit 1302, e.g., on receipt of theinput data from processing element 1320. This may be referred to asInput 1 in FIG. 13. In one embodiment, circuit switched network isconfigured (e.g., programmed) to provide a dedicated communication linebetween processing element 1320 and network dataflow endpoint circuit1306 along path 1316.

When network dataflow endpoint circuit 1304 is to transmit input data tonetwork dataflow endpoint circuit 1302 (e.g., when network dataflowendpoint circuit 1302 has available storage room for the data and/ornetwork dataflow endpoint circuit 1304 has its input data), networkdataflow endpoint circuit 1304 may generate a packet (e.g., includingthe input data and a header to steer that data to network dataflowendpoint circuit 1302 on the packet switched communications network 1314(e.g., as a stop on that (e.g., ring) network 1314). This is illustratedschematically with dashed line 1326 in FIG. 13. Although the exampleshown in FIG. 13 utilizes two sources (e.g., two inputs) a single or anyplurality (e.g., greater than two) of sources (e.g., inputs) may beutilized.

When network dataflow endpoint circuit 1306 is to transmit input data tonetwork dataflow endpoint circuit 1302 (e.g., when network dataflowendpoint circuit 1302 has available storage room for the data and/ornetwork dataflow endpoint circuit 1306 has its input data), networkdataflow endpoint circuit 1304 may generate a packet (e.g., includingthe input data and a header to steer that data to network dataflowendpoint circuit 1302 on the packet switched communications network 1314(e.g., as a stop on that (e.g., ring) network 1314). This is illustratedschematically with dashed line 1318 in FIG. 13. Though a mesh network isshown, other network topologies may be used.

Network dataflow endpoint circuit 1302 (e.g., on receipt of the Input 0from network dataflow endpoint circuit 1304, Input 1 from networkdataflow endpoint circuit 1306, and/or control data) may then performthe programmed dataflow operation (e.g., a Pick operation in thisexample). The network dataflow endpoint circuit 1302 may then output theaccording resultant data from the operation, e.g., to processing element1308 in FIG. 13. In one embodiment, circuit switched network isconfigured (e.g., programmed) to provide a dedicated communication linebetween processing element 1308 (e.g., a buffer thereof) and networkdataflow endpoint circuit 1302 along path 1328. A further example of adistributed Pick operation is discussed below in reference to FIG.26-28.

In one embodiment, the control data to perform an operation (e.g., pickoperation) comes from other components of the spatial array, e.g., aprocessing element or through network. An example of this is discussedbelow in reference to FIG. 14. Note that Pick operator is shownschematically in endpoint 1302, and may not be a multiplexer circuit,for example, see the discussion below of network dataflow endpointcircuit 1400 in FIG. 14.

In certain embodiments, a dataflow graph may have certain operationsperformed by a processing element and certain operations performed by acommunication network (e.g., network dataflow endpoint circuit orcircuits).

FIG. 14 illustrates a network dataflow endpoint circuit 1400 accordingto embodiments of the disclosure. Although multiple components areillustrated in network dataflow endpoint circuit 1400, one or moreinstances of each component may be utilized in a single network dataflowendpoint circuit. An embodiment of a network dataflow endpoint circuitmay include any (e.g., not all) of the components in FIG. 14.

FIG. 14 depicts the microarchitecture of a (e.g., mezzanine) networkinterface showing embodiments of main data (solid line) and control data(dotted) paths. This microarchitecture provides a configuration storageand scheduler to enable (e.g., high-radix) dataflow operators. Certainembodiments herein include data paths to the scheduler to enable legselection and description. FIG. 14 shows a high-level microarchitectureof a network (e.g., mezzanine) endpoint (e.g., stop), which may be amember of a ring network for context. To support (e.g., high-radix)dataflow operations, the configuration of the endpoint (e.g., operationconfiguration storage 1426) to include configurations that examinemultiple network (e.g., virtual) channels (e.g., as opposed to singlevirtual channels in a baseline implementation). Certain embodiments ofnetwork dataflow endpoint circuit 1400 include data paths from ingressand to egress to control the selection of (e.g., pick and switch typesof operations), and/or to describe the choice made by the scheduler inthe case of PickAny dataflow operators or SwitchAny dataflow operators.Flow control and backpressure behavior may be utilized in eachcommunication channel, e.g., in a (e.g., packet switched communications)network and (e.g., circuit switched) network (e.g., fabric of a spatialarray of processing elements).

As one description of an embodiment of the microarchitecture, a pickdataflow operator may function to pick one output of resultant data froma plurality of inputs of input data, e.g., based on control data. Anetwork dataflow endpoint circuit 1400 may be configured to consider oneof the spatial array ingress buffer(s) 1402 of the circuit 1400 (e.g.,data from the fabric being control data) as selecting among multipleinput data elements stored in network ingress buffer(s) 1424 of thecircuit 1400 to steer the resultant data to the spatial array egressbuffer 1408 of the circuit 1400. Thus, the network ingress buffer(s)1424 may be thought of as inputs to a virtual mux, the spatial arrayingress buffer 1402 as the multiplexer select, and the spatial arrayegress buffer 1408 as the multiplexer output. In one embodiment, when a(e.g., control data) value is detected and/or arrives in the spatialarray ingress buffer 1402, the scheduler 1428 (e.g., as programmed by anoperation configuration in storage 1426) is sensitized to examine thecorresponding network ingress channel. When data is available in thatchannel, it is removed from the network ingress buffer 1424 and moved tothe spatial array egress buffer 1408. The control bits of both ingressesand egress may then be updated to reflect the transfer of data. This mayresult in control flow tokens or credits being propagated in theassociated network. In certain embodiment, all inputs (e.g., control ordata) may arise locally or over the network.

Initially, it may seem that the use of packet switched networks toimplement the (e.g., high-radix staging) operators of multiplexed and/ordemultiplexed codes hampers performance. For example, in one embodiment,a packet-switched network is generally shared and the caller and calleedataflow graphs may be distant from one another. Recall, however, thatin certain embodiments, the intention of supporting multiplexing and/ordemultiplexing is to reduce the area consumed by infrequent code pathswithin a dataflow operator (e.g., by the spatial array). Thus, certainembodiments herein reduce area and avoid the consumption of moreexpensive fabric resources, for example, like PEs, e.g., without(substantially) affecting the area and efficiency of individual PEs tosupporting those (e.g., infrequent) operations.

Turning now to further detail of FIG. 14, depicted network dataflowendpoint circuit 1400 includes a spatial array (e.g., fabric) ingressbuffer 1402, for example, to input data (e.g., control data) from a(e.g., circuit switched) network. As noted above, although a singlespatial array (e.g., fabric) ingress buffer 1402 is depicted, aplurality of spatial array (e.g., fabric) ingress buffers may be in anetwork dataflow endpoint circuit. In one embodiment, spatial array(e.g., fabric) ingress buffer 1402 is to receive data (e.g., controldata) from a communications network of a spatial array (e.g., a spatialarray of processing elements), for example, from one or more of network1404 and network 1406. In one embodiment, network 1404 is part ofnetwork 1313 in FIG. 13.

Depicted network dataflow endpoint circuit 1400 includes a spatial array(e.g., fabric) egress buffer 1408, for example, to output data (e.g.,control data) to a (e.g., circuit switched) network. As noted above,although a single spatial array (e.g., fabric) egress buffer 1408 isdepicted, a plurality of spatial array (e.g., fabric) egress buffers maybe in a network dataflow endpoint circuit. In one embodiment, spatialarray (e.g., fabric) egress buffer 1408 is to send (e.g., transmit) data(e.g., control data) onto a communications network of a spatial array(e.g., a spatial array of processing elements), for example, onto one ormore of network 1410 and network 1412. In one embodiment, network 1410is part of network 1313 in FIG. 13.

Additionally or alternatively, network dataflow endpoint circuit 1400may be coupled to another network 1414, e.g., a packet switched network.Another network 1414, e.g., a packet switched network, may be used totransmit (e.g., send or receive) (e.g., input and/or resultant) data toprocessing elements or other components of a spatial array and/or totransmit one or more of input data or resultant data. In one embodiment,network 1414 is part of the packet switched communications network 1314in FIG. 13, e.g., a time multiplexed network.

Network buffer 1418 (e.g., register(s)) may be a stop on (e.g., ring)network 1414, for example, to receive data from network 1414.

Depicted network dataflow endpoint circuit 1400 includes a networkegress buffer 1422, for example, to output data (e.g., resultant data)to a (e.g., packet switched) network. As noted above, although a singlenetwork egress buffer 1422 is depicted, a plurality of network egressbuffers may be in a network dataflow endpoint circuit. In oneembodiment, network egress buffer 1422 is to send (e.g., transmit) data(e.g., resultant data) onto a communications network of a spatial array(e.g., a spatial array of processing elements), for example, ontonetwork 1414. In one embodiment, network 1414 is part of packet switchednetwork 1314 in FIG. 13. In certain embodiments, network egress buffer1422 is to output data (e.g., from spatial array ingress buffer 1402) to(e.g., packet switched) network 1414, for example, to be routed (e.g.,steered) to other components (e.g., other network dataflow endpointcircuit(s)).

Depicted network dataflow endpoint circuit 1400 includes a networkingress buffer 1422, for example, to input data (e.g., inputted data)from a (e.g., packet switched) network. As noted above, although asingle network ingress buffer 1424 is depicted, a plurality of networkingress buffers may be in a network dataflow endpoint circuit. In oneembodiment, network ingress buffer 1424 is to receive (e.g., transmit)data (e.g., input data) from a communications network of a spatial array(e.g., a spatial array of processing elements), for example, fromnetwork 1414. In one embodiment, network 1414 is part of packet switchednetwork 1314 in FIG. 13. In certain embodiments, network ingress buffer1424 is to input data (e.g., from spatial array ingress buffer 1402)from (e.g., packet switched) network 1414, for example, to be routed(e.g., steered) there (e.g., into spatial array egress buffer 1408) fromother components (e.g., other network dataflow endpoint circuit(s)).

In one embodiment, the data format (e.g., of the data on network 1414)includes a packet having data and a header (e.g., with the destinationof that data). In one embodiment, the data format (e.g., of the data onnetwork 1404 and/or 1406) includes only the data (e.g., not a packethaving data and a header (e.g., with the destination of that data)).Network dataflow endpoint circuit 1400 may add (e.g., data output fromcircuit 1400) or remove (e.g., data input into circuit 1400) a header(or other data) to or from a packet. Coupling 1420 (e.g., wire) may senddata received from network 1414 (e.g., from network buffer 1418) tonetwork ingress buffer 1424 and/or multiplexer 1416. Multiplexer 1416may (e.g., via a control signal from the scheduler 1428) output datafrom network buffer 1418 or from network egress buffer 1422. In oneembodiment, one or more of multiplexer 1416 or network buffer 1418 areseparate components from network dataflow endpoint circuit 1400. Abuffer may include a plurality of (e.g., discrete) entries, for example,a plurality of registers.

In one embodiment, operation configuration storage 1426 (e.g., registeror registers) is loaded during configuration (e.g., mapping) andspecifies the particular operation (or operations) this network dataflowendpoint circuit 1400 (e.g., not a processing element of a spatialarray) is to perform (e.g., data steering operations in contrast tologic and/or arithmetic operations). Buffer(s) (e.g., 1402, 1408, 1422,and/or 1424) activity may be controlled by that operation (e.g.,controlled by the scheduler 1428). Scheduler 1428 may schedule anoperation or operations of network dataflow endpoint circuit 1400, forexample, when (e.g., all) input (e.g., payload) data and/or control dataarrives. Dotted lines to and from scheduler 1428 indicate paths that maybe utilized for control data, e.g., to and/or from scheduler 1428.Scheduler may also control multiplexer 1416, e.g., to steer data toand/or from network dataflow endpoint circuit 1400 and network 1414.

In reference to the distributed pick operation in FIG. 13 above, networkdataflow endpoint circuit 1302 may be configured (e.g., as an operationin its operation configuration register 1426 as in FIG. 14) to receive(e.g., in (two storage locations in) its network ingress buffer 1424 asin FIG. 14) input data from each of network dataflow endpoint circuit1304 and network dataflow endpoint circuit 1306, and to output resultantdata (e.g., from its spatial array egress buffer 1408 as in FIG. 14),for example, according to control data (e.g., in its spatial arrayingress buffer 1402 as in FIG. 14). Network dataflow endpoint circuit1304 may be configured (e.g., as an operation in its operationconfiguration register 1426 as in FIG. 14) to provide (e.g., send viacircuit 1304's network egress buffer 1422 as in FIG. 14) input data tonetwork dataflow endpoint circuit 1302, e.g., on receipt (e.g., incircuit 1304's spatial array ingress buffer 1402 as in FIG. 14) of theinput data from processing element 1322. This may be referred to asInput 0 in FIG. 13. In one embodiment, circuit switched network isconfigured (e.g., programmed) to provide a dedicated communication linebetween processing element 1322 and network dataflow endpoint circuit1304 along path 1324. Network dataflow endpoint circuit 1304 may include(e.g., add) a header packet with the received data (e.g., in its networkegress buffer 1422 as in FIG. 14) to steer the packet (e.g., input data)to network dataflow endpoint circuit 1302. Network dataflow endpointcircuit 1306 may be configured (e.g., as an operation in its operationconfiguration register 1426 as in FIG. 14) to provide (e.g., send viacircuit 1306's network egress buffer 1422 as in FIG. 14) input data tonetwork dataflow endpoint circuit 1302, e.g., on receipt (e.g., incircuit 1306's spatial array ingress buffer 1402 as in FIG. 14) of theinput data from processing element 1320. This may be referred to asInput 1 in FIG. 13. In one embodiment, circuit switched network isconfigured (e.g., programmed) to provide a dedicated communication linebetween processing element 1320 and network dataflow endpoint circuit1306 along path 1316. Network dataflow endpoint circuit 1306 may include(e.g., add) a header packet with the received data (e.g., in its networkegress buffer 1422 as in FIG. 14) to steer the packet (e.g., input data)to network dataflow endpoint circuit 1302.

When network dataflow endpoint circuit 1304 is to transmit input data tonetwork dataflow endpoint circuit 1302 (e.g., when network dataflowendpoint circuit 1302 has available storage room for the data and/ornetwork dataflow endpoint circuit 1304 has its input data), networkdataflow endpoint circuit 1304 may generate a packet (e.g., includingthe input data and a header to steer that data to network dataflowendpoint circuit 1302 on the packet switched communications network 1314(e.g., as a stop on that (e.g., ring) network). This is illustratedschematically with dashed line 1326 in FIG. 13. Network 1314 is shownschematically with multiple dotted boxes in FIG. 13. Network 1314 mayinclude a network controller 1314A, e.g., to manage the ingress and/oregress of data on network 1314A.

When network dataflow endpoint circuit 1306 is to transmit input data tonetwork dataflow endpoint circuit 1302 (e.g., when network dataflowendpoint circuit 1302 has available storage room for the data and/ornetwork dataflow endpoint circuit 1306 has its input data), networkdataflow endpoint circuit 1304 may generate a packet (e.g., includingthe input data and a header to steer that data to network dataflowendpoint circuit 1302 on the packet switched communications network 1314(e.g., as a stop on that (e.g., ring) network). This is illustratedschematically with dashed line 1318 in FIG. 13.

Network dataflow endpoint circuit 1302 (e.g., on receipt of the Input 0from network dataflow endpoint circuit 1304 in circuit 1302's networkingress buffer(s), Input 1 from network dataflow endpoint circuit 1306in circuit 1302's network ingress buffer(s), and/or control data fromprocessing element 1308 in circuit 1302's spatial array ingress buffer)may then perform the programmed dataflow operation (e.g., a Pickoperation in this example). The network dataflow endpoint circuit 1302may then output the according resultant data from the operation, e.g.,to processing element 1308 in FIG. 13. In one embodiment, circuitswitched network is configured (e.g., programmed) to provide a dedicatedcommunication line between processing element 1308 (e.g., a bufferthereof) and network dataflow endpoint circuit 1302 along path 1328. Afurther example of a distributed Pick operation is discussed below inreference to FIG. 26-28. Buffers in FIG. 13 may be the small, unlabeledboxes in each PE.

FIGS. 15-8 below include example data formats, but other data formatsmay be utilized. One or more fields may be included in a data format(e.g., in a packet). Data format may be used by network dataflowendpoint circuits, e.g., to transmit (e.g., send and/or receive) databetween a first component (e.g., between a first network dataflowendpoint circuit and a second network dataflow endpoint circuit,component of a spatial array, etc.).

FIG. 15 illustrates data formats for a send operation 1502 and a receiveoperation 1504 according to embodiments of the disclosure. In oneembodiment, send operation 1502 and receive operation 1504 are dataformats of data transmitted on a packed switched communication network.Depicted send operation 1502 data format includes a destination field1502A (e.g., indicating which component in a network the data is to besent to), a channel field 1502B (e.g. indicating which channel on thenetwork the data is to be sent on), and an input field 1502C (e.g., thepayload or input data that is to be sent). Depicted receive operation1504 includes an output field, e.g., which may also include adestination field (not depicted). These data formats may be used (e.g.,for packet(s)) to handle moving data in and out of components. Theseconfigurations may be separable and/or happen in parallel. Theseconfigurations may use separate resources. The term channel maygenerally refer to the communication resources (e.g., in managementhardware) associated with the request. Association of configuration andqueue management hardware may be explicit.

FIG. 16 illustrates another data format for a send operation 1602according to embodiments of the disclosure. In one embodiment, sendoperation 1602 is a data format of data transmitted on a packed switchedcommunication network. Depicted send operation 1602 data format includesa type field (e.g., used to annotate special control packets, such as,but not limited to, configuration, extraction, or exception packets),destination field 1602B (e.g., indicating which component in a networkthe data is to be sent to), a channel field 1602C (e.g. indicating whichchannel on the network the data is to be sent on), and an input field1602D (e.g., the payload or input data that is to be sent).

FIG. 17 illustrates configuration data formats to configure a circuitelement (e.g., network dataflow endpoint circuit) for a send (e.g.,switch) operation 1702 and a receive (e.g., pick) operation 1704according to embodiments of the disclosure. In one embodiment, sendoperation 1702 and receive operation 1704 are configuration data formatsfor data to be transmitted on a packed switched communication network,for example, between network dataflow endpoint circuits. Depicted sendoperation configuration data format 1702 includes a destination field1702A (e.g., indicating which component(s) in a network the (input) datais to be sent to), a channel field 1702B (e.g. indicating which channelon the network the (input) data is to be sent on), an input field 1702C(for example, an identifier of the component(s) that is to send theinput data, e.g., the set of inputs in the (e.g., fabric ingress) bufferthat this element is sensitive to), and an operation field 1702D (e.g.,indicating which of a plurality of operations are to be performed). Inone embodiment, the (e.g., outbound) operation is one of a Switch orSwitchAny dataflow operation, e.g., corresponding to a (e.g., same)dataflow operator of a dataflow graph.

Depicted receive operation configuration data format 1704 includes anoutput field 1704A (e.g., indicating which component(s) in a network the(resultant) data is to be sent to), an input field 1704B (e.g., anidentifier of the component(s) that is to send the input data), and anoperation field 1704C (e.g., indicating which of a plurality ofoperations are to be performed). In one embodiment, the (e.g., inbound)operation is one of a Pick, PickSingleLeg, PickAny, or Merge dataflowoperation, e.g., corresponding to a (e.g., same) dataflow operator of adataflow graph. In one embodiment, a merge dataflow operation is a pickthat requires and dequeues all operands (e.g., with the egress endpointreceiving control).

A configuration data format utilized herein may include one or more ofthe fields described herein, e.g., in any order.

FIG. 18 illustrates a configuration data format 1802 to configure acircuit element (e.g., network dataflow endpoint circuit) for a sendoperation with its input, output, and control data annotated on acircuit 1800 according to embodiments of the disclosure. Depicted sendoperation configuration data format 1802 includes a destination field1802A (e.g., indicating which component in a network the data is to besent to), a channel field 1802B (e.g. indicating which channel on the(packet switched) network the data is to be sent on), and an input field1502C (e.g., an identifier of the component(s) that is to send the inputdata). In one embodiment, circuit 1800 (e.g., network dataflow endpointcircuit) is to receive packet of data in the data format of sendoperation configuration data format 1802, for example, with thedestination indicating which circuit of a plurality of circuits theresultant is to be sent to, the channel indicating which channel of the(packet switched) network the data is to be sent on, and the input beingwhich circuit of a plurality of circuits the input data is to bereceived from. The AND gate 1804 is to allow the operation to beperformed when both the input data is available and the credit status isa yes (for example, the dependency token indicates) indicating there isroom for the output data to be stored, e.g., in a buffer of thedestination. In certain embodiments, each operation is annotated withits requirements (e.g., inputs, outputs, and control) and if allrequirements are met, the configuration is ‘performable’ by the circuit(e.g., network dataflow endpoint circuit).

FIG. 19 illustrates a configuration data format 1902 to configure acircuit element (e.g., network dataflow endpoint circuit) for a selected(e.g., send) operation with its input, output, and control dataannotated on a circuit 1900 according to embodiments of the disclosure.Depicted (e.g., send) operation configuration data format 1902 includesa destination field 1902A (e.g., indicating which component(s) in anetwork the (input) data is to be sent to), a channel field 1902B (e.g.indicating which channel on the network the (input) data is to be senton), an input field 1902C (e.g., an identifier of the component(s) thatis to send the input data), and an operation field 1902D (e.g.,indicating which of a plurality of operations are to be performed and/orthe source of the control data for that operation). In one embodiment,the (e.g., outbound) operation is one of a send, Switch, or SwitchAnydataflow operation, e.g., corresponding to a (e.g., same) dataflowoperator of a dataflow graph.

In one embodiment, circuit 1900 (e.g., network dataflow endpointcircuit) is to receive packet of data in the data format of (e.g., send)operation configuration data format 1902, for example, with the inputbeing the source(s) of the payload (e.g., input data) and the operationfield indicating which operation is to be performed (e.g., shownschematically as Switch or SwitchAny). Depicted multiplexer 1904 mayselect the operation to be performed from a plurality of availableoperations, e.g., based on the value in operation field 1902D. In oneembodiment, circuit 1900 is to perform that operation when both theinput data is available and the credit status is a yes (for example, thedependency token indicates) indicating there is room for the output datato be stored, e.g., in a buffer of the destination.

In one embodiment, the send operation does not utilize control beyondchecking its input(s) are available for sending. This may enable switchto perform the operation without credit on all legs. In one embodiment,the Switch and/or SwitchAny operation includes a multiplexer controlledby the value stored in the operation field 1902D to select the correctqueue management circuitry.

Value stored in operation field 1902D may select among control options,e.g., with different control (e.g., logic) circuitry for each operation,for example, as in FIGS. 20-23. In some embodiments, credit (e.g.,credit on a network) status is another input (e.g., as depicted in FIGS.20-21 here).

FIG. 20 illustrates a configuration data format to configure a circuitelement (e.g., network dataflow endpoint circuit) for a Switch operationconfiguration data format 2002 with its input, output, and control dataannotated on a circuit 2000 according to embodiments of the disclosure.In one embodiment, the (e.g., outbound) operation value stored in theoperation field 1902D is for a Switch operation, e.g., corresponding toa Switch dataflow operator of a dataflow graph. In one embodiment,circuit 2000 (e.g., network dataflow endpoint circuit) is to receive apacket of data in the data format of Switch operation 2002, for example,with the input in input field 2002A being what component(s) are to besent the data and the operation field 2002B indicating which operationis to be performed (e.g., shown schematically as Switch). Depictedcircuit 2000 may select the operation to be executed from a plurality ofavailable operations based on the operation field 2002B. In oneembodiment, circuit 1900 is to perform that operation when both theinput data (for example, according to the input status, e.g., there isroom for the data in the destination(s)) is available and the creditstatus (e.g., selection operation (OP) status) is a yes (for example,the network credit indicates that there is availability on the networkto send that data to the destination(s)). For example, multiplexers2010, 2012, 2014 may be used with a respective input status and creditstatus for each input (e.g., where the output data is to be sent to inthe switch operation), e.g., to prevent an input from showing asavailable until both the input status (e.g., room for data in thedestination) and the credit status (e.g., there is room on the networkto get to the destination) are true (e.g., yes). In one embodiment,input status is an indication there is or is not room for the (output)data to be stored, e.g., in a buffer of the destination. In certainembodiments, AND gate 2006 is to allow the operation to be performedwhen both the input data is available (e.g., as output from multiplexer2004) and the selection operation (e.g., control data) status is a yes,for example, indicating the selection operation (e.g., which of aplurality of outputs an input is to be sent to, see, e.g., FIG. 12). Incertain embodiments, the performance of the operation with the controldata (e.g., selection op) is to cause input data from one of the inputsto be output on one or more (e.g., a plurality of) outputs (e.g., asindicated by the control data), e.g., according to the multiplexerselection bits from multiplexer 2008. In one embodiment, selection opchooses which leg of the switch output will be used and/or selectiondecoder creates multiplexer selection bits.

FIG. 21 illustrates a configuration data format to configure a circuitelement (e.g., network dataflow endpoint circuit) for a SwitchAnyoperation configuration data format 2102 with its input, output, andcontrol data annotated on a circuit 2100 according to embodiments of thedisclosure. In one embodiment, the (e.g., outbound) operation valuestored in the operation field 1902D is for a SwitchAny operation, e.g.,corresponding to a SwitchAny dataflow operator of a dataflow graph. Inone embodiment, circuit 2100 (e.g., network dataflow endpoint circuit)is to receive a packet of data in the data format of SwitchAny operationconfiguration data format 2102, for example, with the input in inputfield 2102A being what component(s) are to be sent the data and theoperation field 2102B indicating which operation is to be performed(e.g., shown schematically as SwitchAny) and/or the source of thecontrol data for that operation. In one embodiment, circuit 1900 is toperform that operation when any of the input data (for example,according to the input status, e.g., there is room for the data in thedestination(s)) is available and the credit status is a yes (forexample, the network credit indicates that there is availability on thenetwork to send that data to the destination(s)). For example,multiplexers 2110, 2112, 2114 may be used with a respective input statusand credit status for each input (e.g., where the output data is to besent to in the SwitchAny operation), e.g., to prevent an input fromshowing as available until both the input status (e.g., room for data inthe destination) and the credit status (e.g., there is room on thenetwork to get to the destination) are true (e.g., yes). In oneembodiment, input status is an indication there is room or is not roomfor the (output) data to be stored, e.g., in a buffer of thedestination. In certain embodiments, OR gate 2104 is to allow theoperation to be performed when any one of the outputs are available. Incertain embodiments, the performance of the operation is to cause thefirst available input data from one of the inputs to be output on one ormore (e.g., a plurality of) outputs, e.g., according to the multiplexerselection bits from multiplexer 2106. In one embodiment, SwitchAnyoccurs as soon as any output credit is available (e.g., as opposed to aSwitch that utilizes a selection op). Multiplexer select bits may beused to steer an input to an (e.g., network) egress buffer of a networkdataflow endpoint circuit.

FIG. 22 illustrates a configuration data format to configure a circuitelement (e.g., network dataflow endpoint circuit) for a Pick operationconfiguration data format 2202 with its input, output, and control dataannotated on a circuit 2200 according to embodiments of the disclosure.In one embodiment, the (e.g., inbound) operation value stored in theoperation field 2202C is for a Pick operation, e.g., corresponding to aPick dataflow operator of a dataflow graph. In one embodiment, circuit2200 (e.g., network dataflow endpoint circuit) is to receive a packet ofdata in the data format of Pick operation configuration data format2202, for example, with the data in input field 2202B being whatcomponent(s) are to send the input data, the data in output field 2202Abeing what component(s) are to be sent the input data, and the operationfield 2202C indicating which operation is to be performed (e.g., shownschematically as Pick) and/or the source of the control data for thatoperation. Depicted circuit 2200 may select the operation to be executedfrom a plurality of available operations based on the operation field2202C. In one embodiment, circuit 2200 is to perform that operation whenboth the input data (for example, according to the input (e.g., networkingress buffer) status, e.g., all the input data has arrived) isavailable, the credit status (e.g., output status) is a yes (forexample, the spatial array egress buffer) indicating there is room forthe output data to be stored, e.g., in a buffer of the destination(s),and the selection operation (e.g., control data) status is a yes. Incertain embodiments, AND gate 2206 is to allow the operation to beperformed when both the input data is available (e.g., as output frommultiplexer 2204), an output space is available, and the selectionoperation (e.g., control data) status is a yes, for example, indicatingthe selection operation (e.g., which of a plurality of outputs an inputis to be sent to, see, e.g., FIG. 12). In certain embodiments, theperformance of the operation with the control data (e.g., selection op)is to cause input data from one of a plurality of inputs (e.g.,indicated by the control data) to be output on one or more (e.g., aplurality of) outputs, e.g., according to the multiplexer selection bitsfrom multiplexer 2208. In one embodiment, selection op chooses which legof the pick will be used and/or selection decoder creates multiplexerselection bits.

FIG. 23 illustrates a configuration data format to configure a circuitelement (e.g., network dataflow endpoint circuit) for a PickAnyoperation 2302 with its input, output, and control data annotated on acircuit 2300 according to embodiments of the disclosure. In oneembodiment, the (e.g., inbound) operation value stored in the operationfield 2302C is for a PickAny operation, e.g., corresponding to a PickAnydataflow operator of a dataflow graph. In one embodiment, circuit 2300(e.g., network dataflow endpoint circuit) is to receive a packet of datain the data format of PickAny operation configuration data format 2302,for example, with the data in input field 2302B being what component(s)are to send the input data, the data in output field 2302A being whatcomponent(s) are to be sent the input data, and the operation field2302C indicating which operation is to be performed (e.g., shownschematically as PickAny). Depicted circuit 2300 may select theoperation to be executed from a plurality of available operations basedon the operation field 2302C. In one embodiment, circuit 2300 is toperform that operation when any (e.g., a first arriving of) the inputdata (for example, according to the input (e.g., network ingress buffer)status, e.g., any of the input data has arrived) is available and thecredit status (e.g., output status) is a yes (for example, the spatialarray egress bufferindicates) indicating there is room for the outputdata to be stored, e.g., in a buffer of the destination(s). In certainembodiments, AND gate 2306 is to allow the operation to be performedwhen any of the input data is available (e.g., as output frommultiplexer 2304) and an output space is available. In certainembodiments, the performance of the operation is to cause the (e.g.,first arriving) input data from one of a plurality of inputs to beoutput on one or more (e.g., a plurality of) outputs, e.g., according tothe multiplexer selection bits from multiplexer 2308.

In one embodiment, PickAny executes on the presence of any data and/orselection decoder creates multiplexer selection bits.

FIG. 24 illustrates selection of an operation (2402, 2404, 2406) by anetwork dataflow endpoint circuit 2400 for performance according toembodiments of the disclosure. Pending operations storage 2401 (e.g., inscheduler 1428 in FIG. 14) may store one or more dataflow operations,e.g., according to the format(s) discussed herein. Scheduler (forexample, based on a fixed priority or the oldest of the operations,e.g., that have all of their operands) may schedule an operation forperformance. For example, scheduler may select operation 2402, andaccording to a value stored in operation field, send the correspondingcontrol signals from multiplexer 2408 and/or multiplexer 2410. As anexample, several operations may be simultaneously executeable in asingle network dataflow endpoint circuit. Assuming all data is there,the “performable” signal (e.g., as shown in FIGS. 18-23) may be input asa signal into multiplexer 2412. Multiplexer 2412 may send as an outputcontrol signals for a selected operation (e.g., one of operation 2402,2404, and 2406) that cause multiplexer 2408 to configure the connectionsin a network dataflow endpoint circuit to perform the selected operation(e.g., to source from or send data to buffer(s)). Multiplexer 2412 maysend as an output control signals for a selected operation (e.g., one ofoperation 2402, 2404, and 2406) that cause multiplexer 2410 to configurethe connections in a network dataflow endpoint circuit to remove datafrom the queue(s), e.g., consumed data. As an example, see thediscussion herein about having data (e.g., token) removed. The “PEstatus” in FIG. 24 may be the control data coming from a PE, forexample, the empty indicator and full indicators of the queues (e.g.,backpressure signals and/or network credit). In one embodiment, the PEstatus may include the empty or full bits for all the buffers and/ordatapaths, e.g., in FIG. 14 herein. FIG. 24 illustrates generalizedscheduling for embodiments herein, e.g., with specialized scheduling forembodiments discussed in reference to FIGS. 20-23.

In one embodiment, (e.g., as with scheduling) the choice of dequeue isdetermined by the operation and its dynamic behavior, e.g., to dequeuethe operation after performance. In one embodiment, a circuit is to usethe operand selection bits to dequeue data (e.g., input, output and/orcontrol data).

FIG. 25 illustrates a network dataflow endpoint circuit 2500 accordingto embodiments of the disclosure. In comparison to FIG. 14, networkdataflow endpoint circuit 2500 has split the configuration and controlinto two separate schedulers. In one embodiment, egress scheduler 2528Ais to schedule an operation on data that is to enter (e.g., from acircuit switched communication network coupled to) the dataflow endpointcircuit 2500 (e.g., at argument queue 2502, for example, spatial arrayingress buffer 1402 as in FIG. 14) and output (e.g., from a packetswitched communication network coupled to) the dataflow endpoint circuit2500 (e.g., at network egress buffer 2522, for example, network egressbuffer 1422 as in FIG. 14). In one embodiment, ingress scheduler 2528Bis to schedule an operation on data that is to enter (e.g., from apacket switched communication network coupled to) the dataflow endpointcircuit 2500 (e.g., at network ingress buffer 2524, for example, networkingress buffer 2424 as in FIG. 14) and output (e.g., from a circuitswitched communication network coupled to) the dataflow endpoint circuit2500 (e.g., at output buffer 2508, for example, spatial array egressbuffer 2408 as in FIG. 14). Scheduler 2528A and/or scheduler 2528B mayinclude as an input the (e.g., operating) status of circuit 2500, e.g.,fullness level of inputs (e.g., buffers 2502A, 2502), fullness level ofoutputs (e.g., buffers 2508), values (e.g., value in 2502A), etc.Scheduler 2528B may include a credit return circuit, for example, todenote that credit is returned to sender, e.g., after receipt in networkingress buffer 2524 of circuit 2500.

Network 2514 may be a circuit switched network, e.g., as discussedherein. Additionally or alternatively, a packet switched network (e.g.,as discussed herein) may also be utilized, for example, coupled tonetwork egress buffer 2522, network ingress buffer 2524, or othercomponents herein. Argument queue 2502 may include a control buffer2502A, for example, to indicate when a respective input queue (e.g.,buffer) includes a (new) item of data, e.g., as a single bit. Turningnow to FIGS. 26-28, in one embodiment, these cumulatively show theconfigurations to create a distributed pick.

FIG. 26 illustrates a network dataflow endpoint circuit 2600 receivinginput zero (0) while performing a pick operation according toembodiments of the disclosure, for example, as discussed above inreference to FIG. 13. In one embodiment, egress configuration 2626A isloaded (e.g., during a configuration step) with a portion of a pickoperation that is to send data to a different network dataflow endpointcircuit (e.g., circuit 2800 in FIG. 28). In one embodiment, egressscheduler 2628A is to monitor the argument queue 2602 (e.g., data queue)for input data (e.g., from a processing element). According to anembodiment of the depicted data format, the “send” (e.g., a binary valuetherefor) indicates data is to be sent according to fields X, Y, with Xbeing the value indicating a particular target network dataflow endpointcircuit (e.g., 0 being network dataflow endpoint circuit 2800 in FIG.28) and Y being the value indicating which network ingress buffer (e.g.,buffer 2824) location the value is to be stored. In one embodiment, Y isthe value indicating a particular channel of a multiple channel (e.g.,packet switched) network (e.g., 0 being channel 0 and/or buffer element0 of network dataflow endpoint circuit 2800 in FIG. 28). When the inputdata arrives, it is then to be sent (e.g., from network egress buffer2622) by network dataflow endpoint circuit 2600 to a different networkdataflow endpoint circuit (e.g., network dataflow endpoint circuit 2800in FIG. 28).

FIG. 27 illustrates a network dataflow endpoint circuit 2700 receivinginput one (1) while performing a pick operation according to embodimentsof the disclosure, for example, as discussed above in reference to FIG.13. In one embodiment, egress configuration 2726A is loaded (e.g.,during a configuration step) with a portion of a pick operation that isto send data to a different network dataflow endpoint circuit (e.g.,circuit 2800 in FIG. 28). In one embodiment, egress scheduler 2728A isto monitor the argument queue 2720 (e.g., data queue 2702B) for inputdata (e.g., from a processing element). According to an embodiment ofthe depicted data format, the “send” (e.g., a binary value therefor)indicates data is to be sent according to fields X, Y, with X being thevalue indicating a particular target network dataflow endpoint circuit(e.g., 0 being network dataflow endpoint circuit 2800 in FIG. 28) and Ybeing the value indicating which network ingress buffer (e.g., buffer2824) location the value is to be stored. In one embodiment, Y is thevalue indicating a particular channel of a multiple channel (e.g.,packet switched) network (e.g., 1 being channel 1 and/or buffer element1 of network dataflow endpoint circuit 2800 in FIG. 28). When the inputdata arrives, it is then to be sent (e.g., from network egress buffer2622) by network dataflow endpoint circuit 2700 to a different networkdataflow endpoint circuit (e.g., network dataflow endpoint circuit 2800in FIG. 28).

FIG. 28 illustrates a network dataflow endpoint circuit 2800 outputtingthe selected input while performing a pick operation according toembodiments of the disclosure, for example, as discussed above inreference to FIG. 13. In one embodiment, other network dataflow endpointcircuits (e.g., circuit 2600 and circuit 2700) are to send their inputdata to network ingress buffer 2824 of circuit 2800. In one embodiment,ingress configuration 2826B is loaded (e.g., during a configurationstep) with a portion of a pick operation that is to pick the data sentto network dataflow endpoint circuit 2800, e.g., according to a controlvalue. In one embodiment, control value is to be received in ingresscontrol 2832 (e.g., buffer). In one embodiment, ingress scheduler 2728Ais to monitor the receipt of the control value and the input values(e.g., in network ingress buffer 2824). For example, if the controlvalue says pick from buffer element A (e.g., 0 or 1 in this example)(e.g., from channel A) of network ingress buffer 2824, the value storedin that buffer element A is then output as a resultant of the operationby circuit 2800, for example, into an output buffer 2808, e.g., whenoutput buffer has storage space (e.g., as indicated by a backpressuresignal). In one embodiment, circuit 2800's output data is sent out whenthe egress buffer has a token (e.g., input data and control data) andthe receiver asserts that it has buffer (e.g., indicating storage isavailable, although other assignments of resources are possible, thisexample is simply illustrative).

FIG. 29 illustrates a flow diagram 2900 according to embodiments of thedisclosure. Depicted flow 2900 includes providing a spatial array ofprocessing elements 2902; routing, with a packet switched communicationsnetwork, data within the spatial array between processing elementsaccording to a dataflow graph 2904; performing a first dataflowoperation of the dataflow graph with the processing elements 2906; andperforming a second dataflow operation of the dataflow graph with aplurality of network dataflow endpoint circuits of the packet switchedcommunications network 2908.

Referring again to FIG. 8, accelerator (e.g., CSA) 802 may perform(e.g., or request performance of) an access (e.g., a load and/or store)of data to one or more of plurality of cache banks (e.g., cache bank808). A memory interface circuit (e.g., request address file (RAF)circuit(s)) may be included, e.g., as discussed herein, to provideaccess between memory (e.g., cache banks) and the accelerator 802.Referring again to FIG. 11, a requesting circuit (e.g., a processingelement) may perform (e.g., or request performance of) an access (e.g.,a load and/or store) of data to one or more of plurality of cache banks(e.g., cache bank 1102). A memory interface circuit (e.g., requestaddress file (RAF) circuit(s)) may be included, e.g., as discussedherein, to provide access between memory (e.g., one or more banks of thecache memory) and the accelerator (e.g., one or more of acceleratortiles (1108, 1110, 1112, 1114)). Referring again to FIGS. 13 and/or 14,a requesting circuit (e.g., a processing element) may perform (e.g., orrequest performance of) an access (e.g., a load and/or store) of data toone or more of a plurality of cache banks. A memory interface circuit(for example, request address file (RAF) circuit(s), e.g., RAF/cacheinterface 1312) may be included, e.g., as discussed herein, to provideaccess between memory (e.g., one or more banks of the cache memory) andthe accelerator (e.g., one or more of the processing elements and/ornetwork dataflow endpoint circuits (e.g., circuits 1302, 1304, 1306)).

In certain embodiments, an accelerator (e.g., a PE thereof) couples to aRAF circuit or a plurality of RAF circuits through (i) a circuitswitched network (for example, as discussed herein, e.g., in referenceto FIGS. 6-11) or (ii) through a packet switched network (for example,as discussed herein, e.g., in reference to FIGS. 12-29)

In certain embodiments, a circuit (e.g., a request address file (RAF)circuit) (e.g., each of a plurality of RAF circuits) includes atranslation lookaside buffer (TLB) (e.g., TLB circuit). TLB may receivean input of a virtual address and output a physical addresscorresponding to the mapping (e.g., address mapping) of the virtualaddress to the physical address (e.g., different than any mapping of adataflow graph to hardware). A virtual address may be an address as seenby a program running on circuitry (e.g., on an accelerator and/orprocessor). A physical address may be an (e.g., different than thevirtual) address in memory hardware. A TLB may include a data structure(e.g., table) to store (e.g., recently used) virtual-to-physical memoryaddress translations, e.g., such that the translation does not have tobe performed on each virtual address present to obtain the physicalmemory address corresponding to that virtual address. If the virtualaddress entry is not in the TLB, a circuit (e.g., a TLB manager circuit)may perform a page walk to determine the virtual-to-physical memoryaddress translation. In one embodiment, a circuit (e.g., a RAF circuit)is to receive an input of a virtual address for translation in a TLB(e.g., TLB in RAF circuit) from a requesting entity (e.g., a PE or otherhardware component) via a circuit switched network, e.g., as in FIGS.6-11. Additionally or alternatively, a circuit (e.g., a RAF circuit) mayreceive an input of a virtual address for translation in a TLB (e.g.,TLB in RAF circuit) from a requesting entity (e.g., a PE, networkdataflow endpoint circuit, or other hardware component) via a packetswitched network, e.g., as in FIGS. 12-29. In certain embodiments, datareceived for a memory (e.g., cache) access request is a memory command.A memory command may include the virtual address to-be-accessed,operation to be performed (e.g., a load or a store), and/or payload data(e.g., for a store).

In certain embodiments, the request data received for a memory (e.g.,cache) access request is received by a request address file circuit orcircuits, e.g., of a configurable spatial accelerator. Certainembodiments of spatial architectures are an energy-efficient andhigh-performance way of accelerating user applications. One of the waysthat a spatial accelerator(s) may achieve energy efficiency is throughspatial distribution, e.g., rather than energy-hungry, centralizedstructures present in cores, spatial architectures may generally usesmall, disaggregated structures (e.g., which are both simpler and moreenergy efficient). For example, the circuit (e.g., spatial array) ofFIG. 11 may spread its load and store operations across several RAFs.This organization may result in a reduction in the size of addresstranslation buffers (e.g., TLBs) at each RAF (e.g., in comparison tousing fewer (or a single) TLB in the RAF). Certain embodiments hereinprovide for distributed coordination for distributed structures (e.g.,distributed TLBs), e.g., in contrast to a local management circuit. Asdiscussed further below, embodiments herein include unified translationlookaside buffer (TLB) management hardware or distributed translationlookaside buffer (TLB) management hardware, e.g., for a shared virtualmemory.

Certain embodiments herein provide for shared virtual memorymicroarchitecture, e.g., that facilitates programming by providing amemory paradigm in the accelerator. Certain embodiments herein do notutilize a monolithic (e.g., single) translation mechanism (e.g., TLB)per accelerator. Certain embodiments herein utilize distributed TLBs,e.g., that are not in the accelerator (e.g., not in the fabric of anaccelerator). Certain embodiments herein provide for a (e.g., complexpart of) the shared virtual memory control to be implemented inhardware. Certain embodiments herein provide the microarchitecture foran accelerator virtual memory translation mechanism. In certainembodiment of this microarchitecture, a distributed set of TLBs areused, e.g., such that many parallel accesses to memory are concurrentlytranslated. To simplify the implementation of the distributed TLBs,certain embodiments herein utilize centralized management hardware(e.g., a TLB manager circuit) to transact certain (e.g., more complex)operations, for example, but not limited to, shootdowns and page walks(e.g., a centralized page walker). To avoid spurious transactions,certain embodiments herein introduce filters (e.g., at the TLB managercircuit) to track the underlying TLBs. Certain embodiments hereinprovide for an accelerator architecture that has been directlyprovisioned with virtual address management hardware, for example,without using remote management hardware (e.g., an input-output memorymanagement unit (IOMMU)) which is shared among multiple (e.g.,area-conscious) accelerators. Certain embodiments herein provide for afull shared virtual memory microarchitecture with tightly coupledtranslation hardware. Certain embodiments herein include (e.g., L1) TLBsthat are tuned for low energy consumption and support relatively fewentries (e.g., 2, 3, 4, 5, 6, 7, or 8 entries per (e.g., L1) TLB). Sometranslations may be shared among the L1 TLBs (e.g., present in multipleL1 TLBs), and a single L2 TLB or plurality of L2 TLBs (e.g., for asingle accelerator and/or accelerator tile) may eliminate spuriousrequests in certain embodiments. Certain embodiments herein provide aunified second level TLB that reduces the number of messages that aresent to handle (e.g., most) translation transactions. Certainembodiments herein greatly simplify the hardware used to implement amultiple level TLB hierarchy. Certain embodiments herein reduce thelatency of completing misses, e.g., misses that involve page walks.

2.6 Translation Lookaside Buffer (TLB) Management Hardware

Certain embodiments herein include multiple TLBs located with a RAFcircuit and a (e.g., single) TLB manager circuit. Certain embodimentsherein include multiple L1 TLB, but as a single, second-level TLB tobalance a desire for low energy usage at the L1 TLB and reduced pagewalks (e.g., for misses in the L1 TLB. Certain embodiments hereinprovide a unified L2 TLB microarchitecture with a single L2 TLB locatedwithin a TLB manager circuit (e.g., hardware block). A (e.g., each of aplurality of) L1 TLB may refer to (e.g. cause an access of) a L2 TLBfirst when a miss occurs, for example, and misses in L2 TLB may resultin the invocation of a page walk. Certain embodiments herein provide adistributed, multiple (e.g., two) level TLB microarchitecture. Certainembodiments of this microarchitecture improve the performance of anaccelerator by reducing the TLB miss penalty of the energy efficient L1TLBs. Messages (e.g., commands) may be carried between the two levelTLBs (e.g., and the page walker) by a network, which may also be sharedwith other (e.g., not translation or not TLB related) memory requests orother system traffic. Page walker may be privileged, for example,operate in privileged mode in contract to a user mode, e.g., page walkermay access page table which is privileged data. In one embodiment withmultiple (e.g., L2) caches, a respective page walker may be included ateach cache. Dotted boxes may indicate optional components (or optionaluse of components) in certain embodiments.

FIG. 30 illustrates a system (e.g., circuit) 3000 with a TLB managercircuit 3010 coupled to a plurality of request address file (RAF)circuits (e.g., RAF circuit (1)) coupled between an accelerator (e.g.,accelerator tile) 3008 and a plurality of cache banks (e.g., includingcache bank 3002) according to embodiments of the disclosure. In oneembodiment, plurality of request address file (RAF) circuits are coupledto plurality of cache banks through an accelerator-cache network 3014(e.g., interconnect). In certain embodiments, accelerator-cache network3014 is further coupled to TLB manager circuit 3010. In certainembodiments, accelerator-cache network 3014 is further coupled to cachehome agent and/or next level cache 3012. In certain embodiments,accelerator-cache network 3014 is separate from any (for example,circuit switched or packet switched) network of an accelerator (e.g.,accelerator tile), e.g., RAF is the interface between the accelerator(e.g., accelerator tile) and the TLB manager circuit 3010. In oneembodiment, a cache home agent is to connect to a memory (e.g., separatefrom the cache banks) to access data from that memory (e.g., memory 202in FIG. 2), e.g., to move data between the cache banks and the (e.g.,system) memory. In one embodiment, a next level cache is a (e.g.,single) higher-level cache, for example, such that the next level cache(e.g., higher-level cache 3012) is checked for data that was not found(e.g., a miss) in a lower-level cache (e.g., cache banks in FIG. 30). Inone embodiment, this data is payload data. In another embodiment, thisdata is a physical address to virtual address mapping. In oneembodiment, a CHA is to perform a search of (e.g., system) memory for amiss (e.g., a miss in the higher-level cache 3012) and not perform asearch for a hit (e.g., the data being requested is in the cache beingsearched).

In one embodiment, a component of accelerator (e.g., accelerator tile)3008 (e.g., one of a distributed set of processing elements) sends arequest (e.g., via a packet switched network and/or circuit switchednetwork of the accelerator) to access a memory location (e.g., virtualaddress), for example, a memory location that is separate from theaccelerator (e.g., accelerator tile). The request may be sent to a RAFcircuit (e.g., RAF circuit 3004). The RAF circuit may check its TLB(e.g., RAF circuit 3004 may check TLB 3006). For a miss for the check, acorresponding command from TLB 3006 (e.g., sent directly to TLB managercircuit 3010 on a dedicated communication line or sent viaaccelerator-cache network 3014) for a miss requesting a physical addressto virtual address translation (e.g., a virtual-to-physical addresstranslation) for the miss from the TLB manager circuit 3010. TLB managercircuit 3010 may then check the cache bank(s) for the translation, forexample, TLB manager circuit 3010 may cause a page walker to perform apage walk in the cache bank(s) and/or other memory locations. Once thetranslation is found (e.g., in cache banks), data (e.g., the valuerepresenting the physical address) may be sent to TLB manager circuit3010 indicating the physical to virtual address translation. Thisinformation may be sent to RAF 3004 (e.g., and installed into its TLB3006). In one embodiment, once the translation is installed in TLB 3006,TLB 3006 may retry the transaction for the previously failingtranslation, e.g., and perform the action on data (e.g., data stored ina cache bank).

Although the number of RAF circuits and cache banks are depicted aseight, any one or plurality of RAF circuits and/or any one or pluralityof cache banks may be utilized in certain embodiments herein. The numberof RAF circuits may be the same or different than the number of cachebanks. A RAF circuit may be coupled to any of the cache banks, e.g., viaaccelerator-cache network 3014. The depicted arrangement of componentsis on example and other arrangements are possible, for example, a nextlevel cache and/or cache home agent (CHA) may be omitted in certainembodiments.

In one embodiment, the requests for data access (e.g., from a respectiveprocessing element of a distributed set of processing elements) areparallel, e.g., and using a distributed address translation. However,some structures, like page walkers, may be expensive, e.g., in terms ofarea utilized in the circuit and/or power. Certain embodiments hereinutilize a distributed architecture with a centralized (e.g., tile) TLBmanager circuit to handle (e.g., complex) transactions. In certainembodiments, each RAF circuit is provisioned with its own TLB, forexample, to achieve high translation bandwidth, e.g., such that each RAFissues at least one physical memory request per cycle. In certainembodiments, TLBs in RAFs are physically distributed and there are manyper accelerator. In one embodiment, a first level (e.g., L1) TLB in aRAF is capable of handling hits, but contacts the TLB manager circuitfor other servicing (e.g., for misses).

In one embodiment, TLBs handle shootdown requests from the tile managercircuit. In one embodiment, the TLB manager circuit services aninvalidate request by invalidating all TLB entries. In anotherembodiment, the TLB chooses to selectively invalidate its TLB entries byperforming a search of its entries for the offending translation, e.g.,and the TLB may also drain all outstanding requests that involve thetranslation. In one embodiment, once a TLB has taken the appropriateaction, it returns a response (e.g., an acknowledgment message) to theTLB manager circuit indicating that it has completed the invalidation.In one embodiment, TLB manager circuit 3010 receives an externalshootdown message and sends shootdown (e.g., invalidate) messages to all(e.g., L1) TLBs (e.g., having or not having a copy of the translation).In one embodiment, TLB manager circuit 3010 receives an externalshootdown message and sends shootdown (e.g., invalidate) messages toeach (e.g., L1) TLB (e.g., TLB 3006) having (e.g., or thought to have) acopy of the translation. A list of the translations in the L1 TLBs maybe kept by the TLB manager circuit. The (e.g., L1) TLBs may sendacknowledgements of invalidation being performed to the TLB managercircuit directly, e.g., on an accelerator-cache network. Upon collectingall acknowledgements, the TLB manager circuit may respond to theinvoking entity indicating the shootdown was completed.

In certain embodiments, a TLB manager circuit is a centralized resourceto transact certain (e.g., uncommon) operations. To enable thiscapability, the TLB manager circuit may be provisioned with ports intothe accelerator cache interconnect (e.g., 3014) by which it is to sendand receive requests and responses. In certain embodiment, a TLB managercircuit is provisioned with a page walker and/or metadata related to theprocess page table. In one embodiment, a page walker is supportsmultiple (e.g., simultaneous) page walks.

In one embodiment, first level (e.g., L1) TLBs (e.g., TLBs 1-6 of RAFsin FIG. 30) send requests to the TLB manager circuit 3010 to servicetheir misses, e.g., and the TLB manager circuit may send requests to theTLBs in the case of rare events, e.g., page table shootdowns or contextswitches. In certain embodiments, the TLBs and TLB manager circuit forma distributed protocol in which the TLB manager circuit receives anexternal request and then transacts that request on the TLBs. In oneembodiment, the TLB manager circuit sends requests to the TLBs andgathers the responses. Upon gathering responses from all TLBs, the TLBmanager circuit will acknowledge the requestor in certain embodiments.In certain embodiments, the TLB manager circuit may use its port tomemory (e.g., not the cache memory) (e.g., port through theaccelerator-cache network 3014) to transact page walks on behalf of theTLBs that it supports.

Certain embodiments herein allow communication between accelerator tilesof a single accelerator, e.g., accelerator tiles (3108A, 3108B, 3108C,3108D) of accelerator 3108 in FIG. 31. Certain embodiments hereininclude hardware (e.g., a TLB manager circuit) with its own page walker,e.g., separate from using a processor core to perform a page walk. Incertain embodiments, a page walk is not performed by a core of aprocessor. As discussed further below, certain embodiments hereinprovide a plurality of levels (e.g., two level) TLB, e.g., that is tiedto a single accelerator.

Unified Higher-Level Translation Lookaside Buffer (TLB) ManagementHardware

Certain embodiments herein include a (e.g., single) higher (e.g.,second) level (e.g., L2) TLB, e.g., that is searched first for a miss ofan input of a virtual address in a (e.g., any of) lower (e.g., first)level (e.g., L1) TLB. A higher-level (e.g., L2) TLB may serve as a cachefor data (e.g., virtual to physical address mappings) in lower-level(e.g., L1) TLBs. The higher-level (e.g., L2) TLB may contain manydifferent translations, arranged, for example, in a fully associativearray. Higher-level (e.g., L2) TLB may be much larger (e.g., includemore mapping entries) than the L1 TLBs and/or serve to share translationamong them. The TLBs may implement fine-grained or coarse-grainedshootdowns. In one embodiment of a fine-grained shootdown, only aparticular address (e.g., mapping) is removed. In one embodiment of acoarse-grained shootdown, all addresses are removed from all TLBs (e.g.,at all levels). In one embodiment to support fine-grained shootdowns, ahigher-level (e.g., L2) TLB is inclusive and tracks which of the L1 TLBshave received particular translations. The higher-level (e.g., L2) TLBentries may include a bit mask representing the location of each L1 TLBtranslation. This representation may be pessimistic, and L1 TLBs maysilently evict translations. However, an implementation may choose tosend messages to the higher-level (e.g., L2) TLB on L1 TLB eviction tomaintain consistency. Certain embodiments herein provide a unified(e.g., single), higher-level TLB, e.g., that handles multiple pagessizes.

FIG. 31 illustrates a system (e.g., circuit) 3100 with a plurality ofrequest address file (RAF) circuits (1) to (16) coupled between anaccelerator 3108 (e.g., having a plurality of accelerator tiles (3108A,3108B, 3108C, 3108D) (e.g., according to any of the disclosure herein))and a plurality of cache banks (1) to (16) (e.g., including cache bank3102 and cache bank 3103) according to embodiments of the disclosure.Cache bank may store operational data (e.g., payload data) and/oraddress translation data (e.g., mapping of a physical address to avirtual address). As discussed herein, a RAF circuit may be as disclosedherein, e.g., as in FIG. 38 discussed below. A component (e.g., PE) mayrequest access to data that is (e.g., or may be) in the plurality ofcache banks, for example, data that is stored external from theaccelerator 3108. In one embodiment, the data request is received by aRAF circuit, e.g., to be queued and/or steered to the correctdestination (e.g., transmitted to that destination via theaccelerator-cache network 3114). Boxes without text in them may be oneor more of a PE, in-fabric storage, and/or communication circuitry, see,e.g., FIG. 30. In one embodiment, the data request includes a virtualaddress (e.g., as used by the components in the accelerator 3108. In oneembodiment, a (e.g., each) RAF circuit includes a TLB (e.g., a firstlevel TLB) that is searched for the physical address corresponding tothat virtual address from the data request. If the physical address ispresent (e.g., there is a hit) in that TLB, the RAF circuit may then usethat physical address to access (e.g., via accelerator-cache network3114) the corresponding storage (e.g., cache bank of banks (1) to (16)to perform the action (e.g., load or store) for that data request atthat physical address. If the physical address is not present (e.g.,there is a miss) in that TLB, the RAF circuit may contact (e.g., viaaccelerator-cache network 3114) TLB manager circuit 3110 for otherservicing. Two, non-limiting examples of servicing are to perform pagewalks or to handle shootdown requests (e.g., from a component separatefrom the system 3100). A page walk may occur upon a miss in a (e.g.,first level (L1)) TLB. For example, RAF 3104 may receive a request(e.g., from accelerator 3108 and/or not on network 3114) to access data.The virtual address for that data access may be checked by the RAF 3104in its TLB 3106. If there is a hit, the data may be accessed per therequest at the physical address corresponding to that virtual address.If there is a miss for that virtual address, in TLB 3106, the RAF 3104and/or its TLB 3106 may then send a request (e.g., which includes themissing virtual address) to the TLB manager circuit 3110. TLB managercircuit 3110 TLB (e.g., page walker (e.g., circuit) 3118 thereof) mayperform a page walk to determine the physical address. The page walker3118 may obtain the physical address for that virtual address, e.g., bytraversing the page table and making requests into the physical memorysystem (e.g., cache and/or memory separate from the cache, e.g., via CHA3112). Once the translation has been obtained, the physical address maythen be forwarded to (e.g., L1) TLB 3106 where it is installed. At thispoint, the TLB 3106 may retry the failing translation which shouldsucceed now, e.g., and the RAF then perform (e.g., via network 3114) theoperation for that physical (e.g., translated) address.

In an embodiment where the TLB manager circuit 3110 includes a (e.g.,single) next (e.g., higher) (e.g., second level (L2)) level TLB, the TLBmanager circuit 3110 may check the higher-level (e.g., L2) TLB for amiss in a (e.g., any) lower-level (e.g., L1) TLB. As depicted in FIG.31, arrow 1 (e.g., indicated by circled 1) may represent a correspondingcommand from TLB 3106 (e.g., sent directly to TLB manager circuit 3110on a dedicated communication line or sent via accelerator-cache network3114) for a miss requesting a physical address to virtual addresstranslation for the miss from the TLB manager circuit 3110. TLB managercircuit 3110 may then check its higher-level (e.g., L2) TLB 3116 for thetranslation. If there is a hit in the higher-level (e.g., L2) TLB 3116for the translation request, the translation data (e.g., physicaladdress) may then be forwarded to (e.g., L1) TLB 3106 where it isinstalled. At this point, the TLB 3106 may retry the failing translationwhich should succeed now, e.g., and the RAF then perform (e.g., vianetwork 3114) the operation for that physical (e.g., translated)address. If there is a miss in the higher-level (e.g., L2) TLB 3116 forthe translation, the page walker 3118 may perform a page walk todetermine the translation (e.g., the physical address corresponding tothe virtual address). In the depicted embodiment, the page walker 3118may traverse the page table, e.g., stored in the cache bank(s). In oneembodiment, the page table is stored in multiple of the cache banks,e.g., pointers stored in one or a subset of the cache banks and the datapointed to be the pointers is stored in another one or another subset ofthe cache banks. In one embodiment, a data structure (e.g., a pagetable) stores the virtual to physical address mappings. In oneembodiment, the data structure is stored in the cache bank. In oneembodiment, a page table is stored in a cache bank and the page walker3118 is to perform a page walk on the page table in the cache bank(s),e.g., to determine a page table entry for the specified virtual address.In one embodiment, the translation is not found in the cache banks, so anext level cache 3112 (e.g., if present) may be searched for thetranslation and/or the CHA 3112 (if present) may search other memory forthe translation, e.g., search memory 202 in FIG. 2. In one embodiment,the translation is found in the cache banks, so the translation is sentto the requesting (e.g., L1) TLB, for example, through L2 TLB.

In the depicted embodiment, arrow 1 (e.g., indicated by circled 1) mayrepresent a corresponding command from TLB 3106 (e.g., sent directly toTLB manager circuit 3110 on a dedicated communication line or sent viaaccelerator-cache network 3114) for a miss requesting a physical addressto virtual address translation for the miss from the TLB manager circuit3110. TLB manager circuit 3110 may then check its higher-level (e.g.,L2) TLB 3116 for the translation, and if not found there, TLB managercircuit 3110 may then check the cache bank(s) for the translation, forexample, TLB manager circuit 3110 may cause page walker 3118 to performa page walk in the cache bank(s) and/or other memory locations. In thedepicted embodiment, TLB manager circuit 3110 (e.g., page walker circuit3118 thereof) is to first search cache bank 3103. In one embodiment, thebank to-be-searched first is determined by the physical address of thepage table root. Certain embodiments herein apply a hash function tosome (e.g., subset of) bits of this physical address, e.g., and therequest is issued by the page walker. In one embodiment, cache bank 3103stores a first level of the data structure storing the addresstranslations, and one or more of the other cache banks (e.g., cache bank3102) stores the next (e.g., lower) level of the data structure storingthe address translations, e.g., according to the layout of the addresstranslation data structure in memory. Arrow 2 (e.g., indicated bycircled 2) may represent a corresponding command from TLB managercircuit 3110 to cache bank 3103 (e.g., sent directly from TLB managercircuit 3110 to cache bank 3103 on a dedicated communication line orsent via accelerator-cache network 3114) to query for the translation(e.g., mapping). Arrow 3 (e.g., indicated by circled 3) may representcache bank 3103 responding with information to the TLB manager circuit3110 indicating which (e.g., other) cache bank (e.g., cache bank 3102 inthe depicted embodiment) is storing the physical to virtual addresstranslation. Arrow 4 (e.g., indicated by circled 4) may represent acorresponding command from TLB manager circuit 3110 to cache bank 3102(e.g., sent directly from TLB manager circuit 3110 to cache bank 3102 ona dedicated communication line or sent via accelerator-cache network3114) to query for the translation. Arrow 5 (e.g., indicated by circled5) may represent cache bank 3102 responding with information to the TLBmanager circuit 3110 indicating the physical to virtual addresstranslation. This information (e.g., mapping) may be inserted into L2TLB 3116, e.g., and then sent (e.g., as represented by arrow 6 (e.g.,indicated by circle 6)) to RAF 3104 (e.g., and installed into its TLB3106). Alternatively, information (e.g., mapping) may be sent to RAF3104 (e.g., and installed into its TLB 3106) without insertion into L2TLB 3116. In one embodiment, once the translation is installed in TLB3106, TLB 3106 may retry the transaction for the previously failingtranslation, e.g., and perform the action on data also stored in a cachebank (e.g., cache bank 1). In certain embodiments, a page walk occursupon a miss in the L2 TLB. The L2 TLB may directly actuate the (e.g.,co-located) page walker, which will transact the page walk and fill theL2 TLB. The L2 TLB may then forward the translation to the L1 TLB. Thepage walker may support multiple simultaneous pages walks. The network(e.g., accelerator-cache network) may be provisioned with physical andvirtual channels such that deadlocks are not possible in the translationflow.

In certain embodiments, an accelerator-cache network (e.g.,interconnect) is to perform actions according to commands, e.g.,commands used on the component of the accelerator-cache network thatinteracts with the TLB manager circuit. The commands may include one ormore of the following: (i) TLB Miss: RAF to TLB manager circuit request.RAF may send a virtual address for which it needs translation. RAF maysend optional data (e.g., metadata) indicating where the translationshould be installed; (ii) TLB Fill: TLB manager circuit to RAF response.TLB manager circuit may send a translation requested back to therequesting RAF (e.g., and return the original metadata sent by the RAF);(iii) TLB Invalidate: TLB manager circuit to RAF Request. TLB managercircuit may inform the RAF of a translation that is being invalidated.In one embodiment, if the RAFs invalidate all entries, no translationfield is utilized (e.g., present); (iv) TLB Invalidate Acknowledgment:RAF to TLB manager circuit response. RAF may acknowledge that it hasremoved the invalid translation and/or drained all outstanding requestsinvolving the translation; and (v) commands for performing a page walk(e.g., as discussed herein).

A TLB manager circuit may receive an external shootdown message (forexample, from a requesting entity, e.g., a component separate from theaccelerator). Shootdown message may come from request external from CSA,for example, an operating system (OS) changing the mapping, e.g., so theshootdown message indicates to clear all the mapping for that page orprocess. TLB manager circuit may send shootdown (e.g., invalidate)messages to each (e.g., L1) TLB having (e.g., or thought to have) a copyof the translation. The (e.g., L1) TLBs may send acknowledgements to theTLB manager circuit directly, e.g., on an accelerator-cache network.Upon collecting all acknowledgements, the TLB manager circuit mayrespond to the invoking entity indicating the shootdown was completed.In the case that an L2 (e.g., if present) is not inclusive, invalidationmessages may be sent to all L1 TLBs.

In certain embodiments of a RAF circuit, two implementations arepossible: coarse and fine. In the fine implementation, a RAF circuit mayexamine its TLB to find the offending translation. If the translation isfound, the RAF circuit may invalidate it, stop issuing new memoryrequests, drain all outstanding memory requests, and/or acknowledge tothe TLB manager circuit that the translation has been removed. In thecoarse implementation, the RAF circuit may halt the issuance of newrequests, invalidate the entire TLB, drain all outstanding requests,and/or acknowledge to the TLB manager circuit that the TLB entries havebeen removed (e.g., for a particular or all TLBs). A TLB manager circuitmay also remove translations from (e.g., all) TLB(s) for an OS lockingpages.

FIG. 32 illustrates a system (e.g., circuit) 3200 with a plurality ofrequest address file (RAF) circuits (1) to (16) coupled between anaccelerator 3208 (e.g., having a plurality of accelerator tiles (3208A,3208B, 3208C, 3208D) (e.g., according to any of the disclosure herein))and a plurality of cache banks (1) to (16) (e.g., including cache bank3202) according to embodiments of the disclosure. Cache bank may storeoperational data (e.g., payload data) and/or address translation data(e.g., mapping of a physical address to a virtual address). Page walker3218 may be optionally present. As discussed herein, a RAF circuit maybe as disclosed herein, e.g., as in FIG. 38 discussed below. In thedepicted embodiment, arrow 1 (e.g., indicated by circled 1) mayrepresent a corresponding shootdown message (e.g., command) to TLBmanager circuit 3210 to perform a shootdown (for example, either on allTLB entries or a particular TLB entry, e.g., as in the course-grainedand fine-grained discussion herein). Boxes without text in them may beone or more of a PE, in-fabric storage and/or communication circuitry,see, e.g., FIG. 30. In one embodiment, a next level cache 3212 and/orCHA 3212 may be utilized, for example, to search for the translation(e.g., the CHA to search memory 202 in FIG. 2).

In one embodiment, when the TLB manager circuit 3210 does not include L2TLB 3216, TLB manager circuit 3210 receives an external shootdownmessage and sends shootdown (e.g., invalidate) messages to all (e.g.,L1) TLBs (e.g., having or not having a copy of the translation). In oneembodiment, when the TLB manager circuit 3210 does not include L2 TLB3216, TLB manager circuit 3210 receives an external shootdown messageand sends shootdown (e.g., invalidate) messages to each (e.g., L1) TLBhaving (e.g., or thought to have) a copy of the translation. A list ofthe translations in the L1 TLBs may be kept by the TLB manager circuit.The (e.g., L1) TLBs may send acknowledgements of invalidation beingperformed to the TLB manager circuit directly, e.g., on anaccelerator-cache network. Upon collecting all acknowledgements, the TLBmanager circuit may respond to the invoking entity indicating theshootdown was completed.

In one embodiment, when the TLB manager circuit 3210 includes L2 TLB3216, TLB manager circuit 3210 receives an external shootdown messageand invalidates the L2 TLB 3216, for example, invalidates all of theentries in that TLB or the entries for a particular translation orsubset of translations (e.g., less than all of the entries) in that TLB.Shootdown messages may also be sent to each L1 TLB thought to have acopy of the translation. The L1 TLBs may send acknowledgements to theTLB manager circuit directly. Upon collecting all acknowledgements, theTLB manager circuit may appropriately respond to the requesting entity.For example, in the case that the L2 TLB is not inclusive, invalidationmessages may be sent to all L1 TLBs. In the depicted embodiment in FIG.32, arrow 1 (e.g., indicated by circled 1) may represent a shootdownmessage being sent and received by TLB manager circuit 3210. If L2 TLB3216 is present or utilized, TLB manager circuit 3210 may invalidate allof the entries in that L2 TLB or the entries for a particulartranslation or subset of translations (e.g., less than all of theentries) in that L2 TLB. In the depicted embodiment, two sets ofshootdown messages and acknowledgments are illustrated, although othernumber of shootdown message and/or acknowledgments are possible. In oneembodiment, TLB manager circuit 3210 includes a list of the RAFs and/orL1 TLBs that include a copy of the entry (e.g., virtual address tophysical address mapping, for example, TLB 3206 in RAF 3204 and TLB 3209in RAF 3207. Arrow 2 (e.g., indicated by circled 2) may represent acorresponding shootdown message (e.g., command) from TLB manager circuit3210 to TLB 3206 in RAF 3204 to perform an invalidation of a mapping(e.g., or invalidate all mapping entries). Arrow 3 (e.g., indicated bycircled 3) may represent TLB 3206 and/or RAF 3204 responding withinformation to the TLB manager circuit 3210 indicating that theshootdown message was received and/or the shootdown (e.g., invalidation)requested was completed at that TLB/RAF. Arrow 4 (e.g., indicated bycircled 4) may represent a corresponding shootdown message (e.g.,command) from TLB manager circuit 3210 to TLB 3209 in RAF 3207 toperform an invalidation of a mapping (e.g., or invalidate all mappingentries). Arrow 5 (e.g., indicated by circled 5) may represent TLB 3209and/or RAF 3207 responding with information to the TLB manager circuit3210 indicating that the shootdown message was received and/or theshootdown (e.g., invalidation) requested was completed at that TLB/RAF.On receipt of all of these acknowledgement messages (e.g., arrow 3 andarrow 5), the TLB manager circuit 3210 may send a shootdown completionacknowledgement message to the requesting entity, for example, asrepresented by arrow 6 (e.g., indicated by circled 6). One or more ofthese communications may occur on a dedicated communication line or sentvia accelerator-cache network 3214.

As shown in certain embodiments herein, a filter circuit (e.g., filtercircuit 3120 in FIG. 31 filter circuit 3220 in FIG. 32) may be included,for example, within TLB manager circuit. In certain embodiments, e.g.,utilizing a plurality of distributed TLBs (e.g., L1 TLBs in RAFs),messages may be sent to the TLBs in case of certain operations, forexample TLB translation invalidations and page walks. In the case ofmany TLBs, the volume of distributed messages may be quite large.Certain embodiments herein include a filter to reduce the volume oftraffic used to manage a distributed (e.g., single or double level) TLBnetwork. In certain (e.g., large) TLB networks, the volume of trafficmay be such that it wastes energy and/or increases the latency ofcompleting the operation(s). Certain embodiments herein reduce thenumber of messages in a distributed TLB for an accelerator (e.g., CSA).

To avoid spurious transactions in a distributed TLB, certain embodimentsherein include filter(s) (e.g., at the TLB manager circuit) to track theunderlying TLBs. In certain embodiments, these filters remove asubstantial number of messages, which may reduce energy and improvelatency. Certain embodiments herein provide for schemes with precise andimprecise tracking. In certain embodiments, imprecise tracking hardwaremay utilize lesser area, but may have some false positives. Certainembodiments herein provide for a shared virtual memorymicroarchitecture. Certain embodiments herein improve the performance ofthese microarchitectures by eliminating spurious traffic. Althoughcertain embodiments are discussed in the context of an accelerator, theymay be applicable to IOMMU based systems. Certain embodiments hereinprevent spurious messaging.

In certain data flows, such as TLB shootdowns, a TLB manager circuit maysend and gather invalidation messages from the distributed (e.g., L1)TLBs. However, sending messages to all TLBs in the belief that one TLBmight contain a translation may be wasteful, e.g., when many or mosttranslation invalidations are not likely to affect the accelerator. SomeTLB organizations may choose to invalidate all translations in responseto any shootdown message. Certain embodiments herein reduce the numberof messages between a TLB manager circuit and TLB to the minimumnecessary to correctly complete a transaction.

Certain embodiments herein include filter hardware at the TLB managercircuit to track and/or filter out shootdown requests such that messagesare only sent to TLBs with the potential to possess the offendingtranslation. Several possible microarchitectures are possible. Forexample, the TLB manager circuit may mirror the entire translation spaceof the distributed TLBs using a content addressable memory (CAM). Asanother example, a counting Bloom filter may be used to track thetranslation space, e.g., checks to see if an address has been seen bythat particular TLB (or all TLBs). In one embodiment, about a fewhundred or thousand of bits is sufficient to maintain a Bloom-stylerepresentation of the L1 TLBs. A filter may be provisioned either perTLB or per accelerator. In one embodiment, a filter maintains arepresentation of the translations it assumes are in the lower-levelTLBs and this may or may not be false-positive-free (e.g., where afilter indicates a translation exists, but a lower-level TLB no longermaintains this translation). This may be used to avoid invalidating thelower-level TLBs.

As the TLB manager circuit supplies TLBs with translations, thesetranslations may be placed into the appropriate filter. The filter(e.g., filter 3220 in FIG. 32) may then be then checked whenever an(e.g., OS) transaction which needs to invalidate arrives at the TLBmanager circuit (e.g., 3210 in FIG. 32). On detection of a potentialconflict by the filter, messages may be sent to the appropriate TLB. Ifthe TLBs invalidate all entries, then the filter may also be cleared atthis time. As shootdowns may generally be infrequent, the cost of thisimplementation may be minor in certain embodiments. Silent evictions maybe permitted at the distributed (e.g., L1) TLBs at the cost of morefrequent false positives. TLB implementations may recognize a falsepositive and cause a re-initialization of the filter.

In certain embodiments, an accelerator-cache network (e.g.,interconnect) is to perform actions according to commands, e.g.,commands used on the component of the accelerator-cache network thatinteracts with the TLB manager circuit. The commands may include one ormore of the following: (i) TLB Evict: RAF circuit to TLB manager circuitresponse. For example, a RAF circuit may inform the TLB manager circuitthat a translation is being removed. This may allow the update of thefilter (e.g., filter 3220 in FIG. 32). In certain embodiments, TLBs mayevict silently, but this may lead to false positives during invalidatesin other embodiments, and/or (ii) TLB Invalidate NACK: RAF circuit toTLB manager circuit response. For example, a RAF circuit may inform theTLB manager circuit that it does not have the address invalidated. RAFcircuit may then send back addresses it does have in subsequent messageso that the TLB manager circuit rebuilds its filter. Certain embodimentsherein allow for the filtering of multiple missing requests. For sharedpages, several TLBs may concurrently attempt to access the samenon-resident translation. To prevent multiple probes for the sametranslation, the L2 TLB may provisionally install the missing page butmark it as under translation. Subsequent accesses to this page may thusbe blocked.

In the embodiments throughout, a depicted number of components may be anexample, and other numbers (e.g., a single or any plurality or anysubset of a plurality) of numbers may be used. For example, the numberof cache banks, RAFs, L1 TLBs, etc. may be any number.

FIG. 33 illustrates a system (e.g., circuit) 3300 with a plurality ofaccelerators 3301A, 3301B, 3301C, and 3301D (e.g., according to any ofthe disclosure herein). Each accelerator is coupled to one or more(e.g., all) of the other tiles through on-die interconnect (ODI). Eachaccelerator may include a plurality of request address file (RAF)circuits coupled between its plurality of accelerator tiles (e.g., tiles3208A, 3208B, 3208C, 3208D in FIG. 32) and a plurality of cache banks(1) to f(16) (e.g., including cache bank ddr3202) according toembodiments of the disclosure. A zoomed in view is provided foraccelerator 3301A. In certain embodiments, each accelerator isidentical. Certain embodiments herein provide for a TLB architecture fora single accelerator as opposed to multiple accelerators, for example, amultiple level TLB (e.g., only used by) for each accelerator. Certainembodiments herein of a distributed TLB architecture for a singleaccelerator allow for the elimination of (e.g., most) process addressspace ID (PASID) handling at the (e.g., L1) TLBs, for example, byconsidering that they belong to a single PASID. Thus, in certainembodiments, no PASID tracking is used in the array (e.g., CSA) (e.g.,fabric) or in the L1 TLB. This may improve the area and energyefficiency of the L1 TLBs. Multiple TLBs may allow the TLBs to besmaller and therefore also save energy. The speed of the accelerator mayalso improve because many translations are concurrently active. Certainembodiments herein include a page walker associated with an L2 TLB. Thismay occur by having a coherent cache beside the management hardware.Page walks may be greatly accelerated as a result of this. Because ofembodiments of the cache organization, it may eliminate the need formemory management unit (MMU) caches. Hints may be included at the L1 TLBto allow a L2 TLB to efficiently examine the correct (e.g., sized) L2TLBs. For example, when there are multiple physical page sizes, a RAFcircuit may only have the virtual address, e.g., because it does nothave the translation, and therefore, it does not know which virtual bitsbelong to the physical mapping and which do not. This means that thetranslation may be homed in several locations in the distributed L2 TLB.However, when there is locality of page size in a channel (e.g., when achannel touching a certain subset (e.g., 2 MB) of data will continue totouch that certain subset (e.g., 2 MB) of data), this information may begiven as a hint to determine the correct L2 TLB.

FIG. 34 illustrates a flow diagram 3400 according to embodiments of thedisclosure. Flow 3400 includes overlaying an input of a dataflow graphcomprising a plurality of nodes into a spatial array of processingelements with each node represented as a dataflow operator in thespatial array of processing elements 3402; coupling a plurality ofrequest address file circuits to the spatial array of processingelements and a cache memory with each request address file circuit ofthe plurality of request address file circuits accessing data in thecache memory in response to a request for data access from the spatialarray of processing elements 3404; providing an output of a physicaladdress for an input of a virtual address into a translation lookasidebuffer of a plurality of translation lookaside buffers comprising atranslation lookaside buffer in each of the plurality of request addressfile circuits 3406; coupling a translation lookaside buffer managercircuit comprising a higher-level translation lookaside buffer than theplurality of translation lookaside buffers to the plurality of requestaddress file circuits and the cache memory 3408; and performing a firstpage walk in the cache memory for a miss of an input of a virtualaddress into a first translation lookaside buffer and into thehigher-level translation lookaside buffer with the translation lookasidebuffer manager circuit to determine a physical address mapped to thevirtual address, and store a mapping of the virtual address to thephysical address from the first page walk in the higher-leveltranslation lookaside buffer to cause the higher-level translationlookaside buffer to send the physical address to the first translationlookaside buffer in a first request address file circuit 3410.

Distributed Higher-Level Translation Lookaside Buffer (TLB) ManagementHardware

Certain embodiments herein include a plurality of higher (e.g., second)level (e.g., L2) TLBs, e.g., where one or more of those TLBs is searchedfirst for a miss of an input of a virtual address in a (e.g., any of)lower (e.g., first) level (e.g., L1) TLB. Higher-level (e.g., L2) TLBsmay serve as a cache for data (e.g., virtual to physical addressmappings) in lower-level (e.g., L1) TLBs. Certain embodiments hereinprovide a distributed L2 TLB microarchitecture. In one embodiment ofthis microarchitecture, higher-level (e.g., L2) TLBs are collocated withcache (e.g., sub-cache) in a cache network, for example, permittingseveral lower-level (e.g., L1) TLB misses to be serviced concurrentlyand/or in a single cycle. Lower-level (e.g., L1) TLBs may searchhigher-level (e.g., L2) TLBs first when a miss occurs. Misses in one ormore of the higher-level (e.g., L2) TLBs may cause the invocation of apage walk. Certain embodiments herein provide for distributedhigher-level (e.g., L2) TLB to simultaneous service a plurality of L1TLB misses (e.g., service more misses than a single higher-level (e.g.,L2) TLB).

Higher-level (e.g., L2) TLBs (e.g., each higher-level TLB) may containmany different translations, arranged, for example, in a fullyassociative array. Higher-level (e.g., L2) TLBs may (e.g., each) be muchlarger (e.g., include more mapping entries) than the L1 TLBs and/orserve to share translation among them. The TLBs may implementfine-grained or coarse-grained shootdowns. In one embodiment of afine-grained shootdown, only a particular address (e.g., mapping) isremoved. In one embodiment of a coarse-grained shootdown, all addressesare removed from all TLBs (e.g., at all levels). In one embodiment tosupport fine-grained shootdowns, higher-level (e.g., L2) TLBs areinclusive and track which of the L1 TLBs have received particulartranslations. The L2 TLB entries may include a bit mask representing thelocation of each L1 TLB translation (e.g., of a single L1 TLB or all L1TLBs). This representation may be pessimistic, and L1 TLBs may silentlyevict. However, an implementation may choose to send messages to the L2TLB on L1 TLB eviction to maintain consistency. Certain embodimentsherein provide distributed (e.g., plurality of) higher-level TLBs, e.g.,that handle multiple pages sizes.

Certain embodiments herein provide for higher-level (e.g., L2) TLBslocated in a cache (e.g., cache banks) and may make use of anaccelerator-cache network provisioned there for communications with thelower-level (e.g., L1) TLBs (e.g., TLBs within a RAF circuit). In oneembodiment, the space covered by each of the L2 TLBs is partitioned byvirtual address space, e.g., with each L2 TLB handling a portion of thevirtual address space selected based on the L1 TLBs. In one embodiment,a hash function is applied at each RAF circuit on the virtual addressneeding translation based on the virtual bits of the virtual addresspage size. In one embodiment, one hash function is used per eachphysical page size.

L2 TLB selection may use low order bits of the virtual address and bedifferent for each supported page size. Certain embodiments hereinprovide a TLB hierarchy to permit each page to have exactly one homeamong the L2 TLBs, e.g., according to the hash function mentioned aboveto force each translation to have a unique home. Alternatively, pagesmay be housed at multiple locations, e.g., to prevent some spurious pagewalks.

FIG. 35 illustrates a system (e.g., circuit) 3500 with a plurality ofrequest address file (RAF) circuits (1) to (6) coupled between anaccelerator 3508 (e.g., having a plurality of processing elements)(e.g., according to any of the disclosure herein) and a plurality ofcache banks (1) to (6) (e.g., including cache bank 3502 and cache bank3505) according to embodiments of the disclosure. Cache bank may storeoperational data (e.g., payload data) and/or address translation data(e.g., mapping of a physical address to a virtual address). As discussedherein, a RAF circuit may be as disclosed herein, e.g., as in FIG. 38discussed below. A component (e.g., PE) may request access to data thatis (e.g., or may be) in the plurality of cache banks, for example, datathat is stored external from the accelerator 3508. In one embodiment,the data request is received by a RAF circuit, e.g., to be queued and/orsteered to the correct destination (e.g., transmitted to thatdestination via the accelerator-cache network 3514). In one embodiment,the data request includes a virtual address (e.g., as used by thecomponents in the accelerator 3508. In one embodiment, a (e.g., each)RAF circuit includes a TLB (e.g., a first level TLB) that is searchedfor the physical address corresponding to that virtual address from thedata request. If the physical address is present (e.g., there is a hit)in that TLB, the RAF circuit may then use that physical address toaccess (e.g., via accelerator-cache network 3514) the correspondingstorage (e.g., cache bank of banks (1)-(6) to perform the action (e.g.,load or store) for that data request at that physical address. If thephysical address is not present (e.g., there is a miss) in thatlower-level (e.g., L1) TLB, the RAF circuit may contact (e.g., viaaccelerator-cache network 3514) a higher-level (e.g., L2) TLB. In oneembodiment, this is determined by the hash function which maps certainvirtual address bits to a cache bank responsible for handling thatvirtual address range. In one embodiment, to handle multiple page sizes,multiple hash functions are utilized, e.g., one for each page size.Certain embodiments herein add the (e.g., low order) bits discussedabove to improve the likelihood of selecting the correct cache bank.

If the physical address is not present (e.g., there is a miss) in thathigher-level (e.g., L2) TLB, the RAF circuit may contact (e.g., viaaccelerator-cache network 3514) TLB manager circuit 3210 for otherservicing. Two, non-limiting examples of servicing are to perform pagewalks or to handle shootdown requests (e.g., from a component separatefrom the system 3100). A page walk may occur upon a miss in a (e.g.,second level (L2)) TLB. For example, RAF 3504 may receive a request(e.g., from accelerator 3508 and/or not on network 3514) to access data.The virtual address for that data access may be checked by the RAF 3504in its TLB 3506. If there is a hit, the data may be accessed per therequest at the physical address corresponding to that virtual address.If there is a miss for that virtual address, in TLB 3506, the RAF 3504and/or its TLB 3506 may then send a request (e.g., which includes themissing virtual address) to its next level (e.g., L2) TLB in the cachebank. In the depicted embodiment, the request is sent to cache bank 3502(e.g., to L2 TLB LMF03 within cache bank 3502). If there is a hit in thehigher-level (e.g., L2) TLB 3503 for the translation, the translationdata (e.g., physical address) may then be forwarded (e.g., viaaccelerator-cache network 3514) to (e.g., L1) TLB 3506 where it isinstalled. At this point, the TLB 3506 may retry the failing translationwhich should succeed now, e.g., and the RAF 3504 then perform (e.g., vianetwork 3514) the operation for that physical (e.g., translated)address. If there is a miss in the higher-level (e.g., L2) TLB 3503 forthe translation request, the translation request (e.g., virtual address)may then be forwarded (e.g., via accelerator-cache network 3514) (e.g.,by TLB 3503) to TLB manager circuit 3510. TLB manager circuit 3510 TLB(e.g., page walker (e.g., circuit) 3518 thereof) may perform a page walkto determine the physical address. The page walker 3518 may obtain thephysical address for that virtual address, e.g., by traversing the pagetable and making requests into the physical memory system (e.g., cacheand/or memory separate from the cache, e.g., via CHA 3512). Once thetranslation has been obtained, the physical address may then beforwarded to higher-level (e.g., L2) TLB 3503 where it is installed.Installing of physical address (e.g., mapping) in higher-level (e.g.,L2) TLB 3503 may cause the physical address (e.g., mapping) to be sentto and installed into (e.g., requesting) lower-level (e.g., L1) TLB3506. At this point, the TLB 3506 may retry the failing translationwhich should succeed now, e.g., and the RAF 3504 then perform (e.g., vianetwork 3114) the operation for that physical (e.g., translated)address. Boxes without text in them may be one or more of PE, in-fabricstorage, and/or communication circuitry, see, e.g., FIG. 30.

In an embodiment where the TLB manager circuit 3510 includes a pluralityof (e.g., distributed) next (e.g., higher) (e.g., second level (L2))level TLBs, the TLB manager circuit 3510 may check the (e.g., one ormore (e.g., all) of the other) higher-level (e.g., L2) TLBs for a missin a (e.g., any) lower-level (e.g., L1) TLB and/or higher-level (e.g.,L2) TLB. As depicted in FIG. 35, arrow 1 (e.g., indicated by circled 1)may represent a corresponding command from lower-level (e.g., L1) TLB3506 (e.g., sent directly to higher-level (e.g., L2) TLB 3503 on adedicated communication line or sent via accelerator-cache network 3514)for a miss requesting a physical address to virtual address translationfor the miss. If there is a hit in the higher-level (e.g., L2) TLB 3503for the translation request, the translation data (e.g., physicaladdress) is forwarded (e.g., on a dedicated communication line or sentvia accelerator-cache network 3514) to lower-level (e.g., L1) TLB 3506where it is installed, e.g., as represented by arrow 6 (e.g., indicatedby circled 6). At this point, the TLB 3506 may retry the failingtranslation which should succeed now, e.g., and the RAF LMF04 thenperform (e.g., via network 3514) the operation for that physical (e.g.,translated) address. If there is a miss in the higher-level (e.g., L2)TLB 3503 for the translation request, the translation request (e.g.,virtual address) is forwarded (e.g., on a dedicated communication lineor sent via accelerator-cache network 3514) to TLB manager circuit 3510,e.g., as represented by arrow 2 (e.g., indicated by circled 2). If thereis a miss in the higher-level (e.g., L2) TLB 3503 for the translation,the page walker 3518 may perform a page walk to determine thetranslation (e.g., the physical address corresponding to the virtualaddress), for example, be sending a (e.g., page walk) command to cachebank 3505 and/or higher-level (e.g., L2) TLB 3507 in cache bank 3505,e.g., as represented by arrow 3 (e.g., indicated by circled 3) andhigher-level (e.g., L2) TLB 3507 is to send the translation (e.g., thephysical address corresponding to the virtual address) to TLB managercircuit 3510 (e.g., to its page walker 3518), e.g., as represented byarrow 4 (e.g., indicated by circled 4). In the depicted embodiment, thepage walker 3518 may traverse the next level TLB and/or page table,e.g., stored in the higher-level (e.g., L2) cache bank(s). In oneembodiment, the page table is stored in multiple of the cache banks,e.g., pointers stored in one or a subset of the cache banks and the datapointed to be the pointers is stored in another one or another subset ofthe cache banks. In one embodiment, a data structure (e.g., a pagetable) stores the virtual to physical address mappings. In oneembodiment, the data structure is stored in the cache bank(s). In oneembodiment, a page table is stored in a cache bank and the page walker3518 is to perform a page walk on the page table in the cache bank(s),e.g., to determine a page table entry for the specified virtual address.In one embodiment, the translation is not found in the cache banks, so afurther next level cache 3512 (e.g., if present) may be searched for thetranslation and/or the CHA LMFB12 (if present) may search other memoryfor the translation, e.g., search memory 202 in FIG. 2. In oneembodiment, the translation is found in the cache banks, so thetranslation is sent to the requesting (e.g., L1) TLB, for example,through L2 TLB. Arrow 5 (e.g., indicated by circled 5) may represent TLBmanager circuit 3510 (e.g., its page walker 3518) responding withinformation to the cache bank 3502 (e.g., its higher-level (e.g., L2)TLB 3503) indicating the physical to virtual address translation. Thisinformation (e.g., mapping) may be inserted into L2 TLB 3503, e.g., andthen sent (e.g., as represented by arrow 6 (e.g., indicated by circle6)) to RAF 3504 (e.g., and installed into its TLB 3506). Alternatively,information (e.g., mapping) may be sent to RAF 3504 (e.g., and installedinto its TLB 3506) without insertion into higher-level (e.g., L2) TLB3503. In one embodiment, once the translation is installed in TLB 3506,TLB 3506 may retry the transaction for the previously failingtranslation, e.g., and perform the action on data also stored in a cachebank (e.g., cache bank 1). In certain embodiments, a page walk occursupon a miss in the higher-level (e.g., L2) TLB or TLBs. Higher-level(e.g., L2) TLB or TLBs may directly actuate the page walker, e.g., whichwill transact the page walk and fill the higher-level (e.g., L2) TLB orTLBs. The higher-level (e.g., L2) TLB or TLBs may then forward thetranslation to the L1 TLB. The page walker may support multiplesimultaneous pages walks. The network (e.g., accelerator-cache network)may be provisioned with physical and/or virtual channels such thatdeadlocks are not possible in the translation flow. In one embodiment,the page size is unknown to the lower-level (e.g., L1) TLB request, soit may be possible that the L1 TLB misspeculated the L2 TLB home of thetranslation. However, the page walk may resolve the translation,determine the page size, and therefore install the page in the desired(e.g., correct) L2 TLB. The page walker may issue messages to multipleL2 TLBs in this case. Alternatively, the page may be installed atmultiple locations.

In certain embodiments, an accelerator-cache network (e.g.,interconnect) is to perform actions according to commands, e.g.,commands used on the component of the accelerator-cache network thatinteracts with the TLB manager circuit. The commands may include one ormore of the following: (i) Page Walk Miss-speculate: tile manager to L2TLB. The page walker may discover that the lower-level (e.g., L1) TLBhas wrongly speculated and sends a message to the requestinghigher-level (e.g., L2) TLB. Requesting higher-level (e.g., L2) TLB mayreturn the translation to the lower-level (e.g., L1) TLB but does notinstall it; (ii) Page Walk Install: tile manager to higher-level (e.g.,L2) TLB. The page walker may discover that the lower-level (e.g., L1)TLB has wrongly speculated and sends an installation request to thecorrect higher-level (e.g., L2) TLB; and (iii) commands for performing apage walk (e.g., as discussed herein).

One parameter in distributing higher-level (e.g., L2) TLBs may bedeciding which (e.g., single) higher-level (e.g., L2) TLB(s) should bequeried on a miss from a particular lower-level (e.g., L1) TLB(s). On alower-level (e.g., L1) TLB miss, the virtual address being queried maybe available; the page size, and consequently the L2 TLB expected tohome the mapping for the virtual address, may be unknown. Thelower-level (e.g., L1) TLB may send requests to each of the higher-level(e.g., L2) TLBs where the translation might reside, e.g., up to onelocation per translation home. However, in certain embodiments it ispossible to greatly reduce the number of messages sent to thehigher-level (e.g., L2) TLBs by speculating the correct home. Forexample, the lower-level (e.g., L1) TLB may retain a representation ofthe size of the last page accessed and from this determine which pagesize to access. There may be a strong locality of page size inaccelerators, making this mechanism quite effective in certainembodiments.

Back invalidations may occur when an eviction occurs at a higher-level(e.g., L2) TLB. When the L2 TLB evicts a translation, it may send ashootdown signal for that translation to (e.g., all) lower-level (e.g.,L1) TLBs that contain the translation. Back invalidations may be usedwhen precise shootdowns are used. If blanket shootdowns are issued toall the lower-level (e.g., L1) TLBs, fine-grained shootdowns may not beused in certain embodiments.

A TLB manager circuit may receive an external shootdown message (forexample, from a requesting entity, e.g., a component separate from theaccelerator). Shootdown message may come from request external from CSA,for example, an operating system (OS) changing the mapping, e.g., so theshootdown message indicates to clear all the mapping for that page orprocess. TLB manager circuit may send shootdown (e.g., invalidate)messages to each (e.g., L1 and L2) TLB having (e.g., or thought to have)a copy of the translation. The (e.g., L1 and L2) TLBs may sendacknowledgements to the TLB manager circuit directly, e.g., on anaccelerator-cache network. Upon collecting all acknowledgements, the TLBmanager circuit may respond to the invoking entity indicating theshootdown was completed. In the case that an L2 (e.g., if present) isnot inclusive, invalidation messages may be sent to all L1 TLBs.

In certain embodiments of a RAF circuit, two implementations arepossible: coarse and fine. In the fine implementation, a RAF circuit mayexamine its TLB to find the offending translation. If the translation isfound, the RAF circuit may invalidate it, stop issuing new memoryrequests, drain all outstanding memory requests, and/or acknowledge tothe TLB manager circuit that the translation has been removed. In thecoarse implementation, the RAF circuit may halt the issuance of newrequests, invalidate the entire TLB, drain all outstanding requests,and/or acknowledge to the TLB manager circuit that the TLB entries havebeen removed (e.g., for a particular or all TLBs). A TLB manager circuitmay also remove translations from (e.g., all) TLB(s) for an OS lockingpages

FIG. 36 illustrates a system (e.g., circuit) 3600 with a plurality ofrequest address file (RAF) circuits (1) to (16) coupled between anaccelerator 3608 (e.g., having a plurality of accelerator tiles (3208A,3208B, 3208C, 3208D) and a plurality of cache banks (1) to (16) (e.g.,including cache bank 3602) according to embodiments of the disclosure.Cache bank may store operational data (e.g., payload data) and/oraddress translation data (e.g., mapping of a physical address to avirtual address). Page walker 3618 may be optionally present. Asdiscussed herein, a RAF circuit may be as disclosed herein, e.g., as inFIG. 38 discussed below. In the depicted embodiment, arrow 1 (e.g.,indicated by circled 1) may represent a corresponding shootdown message(e.g., command) to TLB manager circuit 3610 to perform a shootdown (forexample, either on all TLB entries or a particular TLB entry, e.g., asin the course-grained and fine-grained discussion herein). Boxes withouttext in them may be one or more of PE, in-fabric storage, and/orcommunication circuitry, see, e.g., FIG. 30. In one embodiment, a nextlevel cache 3612 and/or CHA 3612 may be utilized, for example, to searchfor the translation (e.g., the CHA to search memory 202 in FIG. 2).

In one embodiment, when system 3600 does not include L2 TLBs, TLBmanager circuit 3610 receives an external shootdown message and sendsshootdown (e.g., invalidate) messages to all (e.g., L1) TLBs (e.g.,including TLB 3606 and TLB 3609) (e.g., having or not having a copy ofthe translation). In one embodiment, when system 3600 does not includeL2 TLBs, TLB manager circuit 3610 receives an external shootdown messageand sends shootdown (e.g., invalidate) messages to each (e.g., L1) TLBhaving (e.g., or thought to have) a copy of the translation. A list ofthe translations in the L1 TLBs may be kept by the TLB manager circuit.The (e.g., L1) TLBs may send acknowledgements of invalidation beingperformed to the TLB manager circuit directly, e.g., on anaccelerator-cache network. Upon collecting all acknowledgements, the TLBmanager circuit may respond to the invoking entity indicating theshootdown was completed.

In one embodiment, when the system 3600 includes L2 TLBs (e.g.,including L2 TLB 3603), TLB manager circuit 3610 receives an externalshootdown message and invalidates the L2 TLB 3603, for example,invalidates all of the entries in that TLB or the entries for aparticular translation or subset of translations (e.g., less than all ofthe entries) in that TLB. Shootdown messages may also be sent to each L1and/or L2 TLB thought to have a copy of the translation. In oneembodiment, the TLB manager circuit is to send a shootdown message to anL2 TLB, and the L2 TLB may then send a shootdown message to each L1 TLB.The L1 TLBs may send acknowledgements to the TLB manager circuitdirectly. Upon collecting all acknowledgements, the TLB manager circuitmay appropriately respond to the requesting entity. For example, in thecase that an L2 TLB is not inclusive, invalidation messages may be sentto all L1 TLBs.

In the depicted embodiment in FIG. 36, arrow 1 (e.g., indicated bycircled 1) may represent a shootdown message being sent and received byTLB manager circuit 3610. TLB manager circuit 3210 may determine which(if any) of the L2 TLBs include a copy of the translation to be shotdown. In the depicted embodiment, TLB manager circuit 3210 send ashootdown message to L2 TLB 3603 (e.g., within cache bank 3602) toinvalidate all of the entries in that L2 TLB or the entries for aparticular translation or subset of translations (e.g., less than all ofthe entries) in that L2 TLB. L2 TLB 3603 (e.g., cache bank 3602) maythen send shootdown message to each (e.g., all) L1 TLBs. In the depictedembodiment, two sets of shootdown messages and acknowledgments areillustrated, although other number of shootdown message and/oracknowledgments are possible. In one embodiment, TLB manager circuit3210 and/or L2 TLBs includes a list of the RAFs and/or L1 TLBs thatinclude a copy of the entry (e.g., virtual address to physical addressmapping. Arrow 2 (e.g., indicated by circled 2) may represent acorresponding shootdown message (e.g., command) from TLB manager circuit3610 to L2 TLB 3603 in cache bank 3602 to perform an invalidation of amapping (e.g., or invalidate all mapping entries). Arrow 3 (e.g.,indicated by circled 3) may represent higher-level (e.g., L2) TLB 3603and/or cache bank 3602 responding with information to the TLB managercircuit 3610 indicating that the shootdown message was received by TLB3603 and/or cache bank 3602 (for example, and including the number ofmessages expected back from lower-level (e.g., L1) TLBs, e.g., thenumber of L1 TLBs including the translation). In the depictedembodiment, the translation that is to be shot down (e.g., removed) forthe request at arrow 1 may be (e.g., as indicated by L2 TLB 3603) in L1TLB 3606 in RAF 3604 and TLB 3609 in RAF 3607. Arrow 4 (e.g., indicatedby circled 4) may represent a corresponding shootdown message (e.g.,command) from L2 TLB 3603 (e.g., cache bank 3602) to TLB 3606 in RAF3604 to perform an invalidation of a mapping (e.g., or invalidate allmapping entries). Arrow 5 (e.g., indicated by circled 5) may represent acorresponding shootdown message (e.g., command) from L2 TLB 3603 (e.g.,cache bank 3602) to TLB 3609 in RAF 3607 to perform an invalidation of amapping (e.g., or invalidate all mapping entries). Arrow 3communications may occur before, after, or during other communications(e.g., communications for arrow 4 and/or arrow 5). Arrow 6 (e.g.,indicated by circled 6) may represent TLB 3606 and/or RAF 3604responding with information to the TLB manager circuit 3610 indicatingthat the shootdown message was received at TLB 3606 and/or RAF 3604and/or the shootdown (e.g., invalidation) requested was completed at TLB3606 and/or RAF 3604. Arrow 7 (e.g., indicated by circled 7) mayrepresent TLB 3609 and/or RAF 3607 responding with information to theTLB manager circuit 3610 indicating that the shootdown message wasreceived at TLB 3609 and/or RAF 3607 and/or the shootdown (e.g.,invalidation) requested was completed at TLB 3609 and/or RAF 3607. Onreceipt of all of these acknowledgement messages (e.g., arrow 6 andarrow 7), the TLB manager circuit 3610 may send a shootdown completionacknowledgement message to the requesting entity, for example, asrepresented by arrow 8 (e.g., indicated by circled 8). One or more ofthese communications may occur on a dedicated communication line or sentvia accelerator-cache network 3614.

As shown in certain embodiments herein, a filter circuit (e.g., filtercircuit 3620 in FIG. 36) may be included, for example, within TLBmanager circuit. In certain embodiments, e.g., utilizing a plurality ofdistributed TLBs (e.g., L1 TLBs in RAFs and/or L2 TLBs in cache banks),messages may be sent to the TLBs in case of certain operations, forexample TLB translation invalidations and page walks. In the case ofmany TLBs, the volume of distributed messages may be quite large.Certain embodiments herein include a filter to reduce the volume oftraffic used to manage a distributed (e.g., single or double level) TLBnetwork. In certain (e.g., large) TLB networks, the volume of trafficmay be such that it wastes energy and/or increases the latency ofcompleting the operation(s). Certain embodiments herein reduce thenumber of messages in a distributed TLB for an accelerator (e.g., CSA).

To avoid spurious transactions in a distributed TLB, certain embodimentsherein include filter(s) (e.g., at the TLB manager circuit) to track theunderlying TLBs. In certain embodiments, these filters remove asubstantial number of messages, which may reduce energy and improvelatency. Certain embodiments herein provide for schemes with precise andimprecise tracking. In certain embodiments, imprecise tracking hardwaremay utilize lesser area, but may have some false positives. Certainembodiments herein provide for a shared virtual memorymicroarchitecture. Certain embodiments herein improve the performance ofthese microarchitectures by eliminating spurious traffic. Althoughcertain embodiments are discussed in the context of an accelerator, theymay be applicable to IOMMU based systems. Certain embodiments hereinprevent spurious messaging.

In certain data flows, such as TLB shootdowns, a TLB manager circuit maysend and gather invalidation messages from the distributed (e.g., L1)TLBs. However, sending messages to all TLBs in the belief that one TLBmight contain a translation may be wasteful, e.g., when many or mosttranslation invalidations are not likely to affect the accelerator. SomeTLB organizations may choose to invalidate all translations in responseto any shootdown message. Certain embodiments herein reduce the numberof messages between a TLB manager circuit and TLB to the minimumnecessary to correctly complete a transaction.

Certain embodiments herein include filter hardware at the TLB managercircuit to track and/or filter out shootdown requests such that messagesare only sent to TLBs with the potential to possess the offendingtranslation. Several possible microarchitectures are possible. Forexample, the TLB manager circuit may mirror the entire translation spaceof the distributed TLBs using a content addressable memory (CAM). Asanother example, a counting Bloom filter may be used to track thetranslation space. In one embodiment, about a few hundred or thousand ofbits is sufficient to maintain a Bloom-style representation of the L1TLBs. A filter may be provisioned either per TLB or per accelerator.

As the TLB manager circuit supplies TLBs with translations, thesetranslations may be placed into the appropriate filter. The filter(e.g., filter 3620 in FIG. 36) may then be then checked whenever an(e.g., OS) transaction which needs to invalidate arrives at the TLBmanager circuit (e.g., 3610 in FIG. 36). On detection of a potentialconflict by the filter, messages may be sent to the appropriate (e.g.,L2) TLB. If the TLBs invalidate all entries, then the filter may also becleared at this time. As shootdowns may generally be infrequent, thecost of this implementation may be minor in certain embodiments. Silentevictions may be permitted at the distributed (e.g., L1 or L2) TLBs atthe cost of more frequent false positives. TLB implementations mayrecognize a false positive and cause a re-initialization of the filter.

In certain embodiments, an accelerator-cache network (e.g.,interconnect) is to perform actions (e.g., on the L1 TLBs) according tocommands, e.g., commands used on the component of the accelerator-cachenetwork that interacts with the TLB manager circuit. The commands mayinclude one or more of the following: (i) TLB Evict: RAF circuit to TLBmanager circuit response. For example, a RAF circuit may inform the TLBmanager circuit that a translation is being removed. This may allow theupdate of the filter (e.g., filter 3520 in FIG. 35). In certainembodiments, TLBs may evict silently, but this may lead to falsepositives during invalidates in other embodiments, and/or (ii) TLBInvalidate NACK: RAF circuit to TLB manager circuit response. Forexample, a RAF circuit may inform the TLB manager circuit that it doesnot have the address invalidated. RAF circuit may then send backaddresses it does have in subsequent message so that the TLB managercircuit rebuilds its filter. Certain embodiments herein allow for thefiltering of multiple missing requests. For shared pages, several TLBsmay concurrently attempt to access the same non-resident translation. Toprevent multiple probes for the same translation, the L2 TLB(s) mayprovisionally install the missing page but mark it as under translation.Subsequent accesses to this page may thus be blocked.

In the embodiments throughout, a depicted number of components may be anexample, and other numbers (e.g., a single or any plurality or anysubset of a plurality) of numbers may be used. For example, the numberof cache banks, RAFs, L1 TLBs, L2 TLBs, etc. may be any number.

FIG. 37 illustrates a flow diagram 3700 according to embodiments of thedisclosure. Flow 3700 includes overlaying an input of a dataflow graphcomprising a plurality of nodes into a spatial array of processingelements with each node represented as a dataflow operator in thespatial array of processing elements 3702; coupling a plurality ofrequest address file circuits to the spatial array of processingelements and a plurality of cache memory banks with each request addressfile circuit of the plurality of request address file circuits accessingdata in the plurality of cache memory banks in response to a request fordata access from the spatial array of processing elements 3704;providing an output of a physical address for an input of a virtualaddress into a translation lookaside buffer of a plurality oftranslation lookaside buffers comprising a translation lookaside bufferin each of the plurality of request address file circuits 3706;providing an output of a physical address for an input of a virtualaddress into a higher-level, than the plurality of translation lookasidebuffers, translation lookaside buffer of a plurality of higher-leveltranslation lookaside buffers comprising a higher-level translationlookaside buffer in each of the plurality of cache memory banks 3708;coupling a translation lookaside buffer manager circuit to the pluralityof request address file circuits and the plurality of cache memory banks3710; and performing a first page walk in the plurality of cache memorybanks for a miss of an input of a virtual address into a firsttranslation lookaside buffer and into a first higher-level translationlookaside buffer with the translation lookaside buffer manager circuitto determine a physical address mapped to the virtual address, and storea mapping of the virtual address to the physical address from the firstpage walk in the first higher-level translation lookaside buffer tocause the first higher-level translation lookaside buffer to send thephysical address to the first translation lookaside buffer in a firstrequest address file circuit 3712.

RAF Circuit with TLB

A request address file (RAF) circuit, a simplified version of which isshown in FIG. 38, may be responsible for executing memory operations andserves as an intermediary between the CSA fabric and the memoryhierarchy. As such, the main microarchitectural task of the RAF may beto rationalize the out-of-order memory subsystem with the in-ordersemantics of CSA fabric. In this capacity, the RAF circuit may beprovisioned with completion buffers, e.g., queue-like structures thatre-order memory responses and return them to the fabric in the requestorder. The second major functionality of the RAF circuit may be toprovide support in the form of address translation and a page walker.Incoming virtual addresses may be translated to physical addresses usinga channel-associative translation lookaside buffer (TLB). To provideample memory bandwidth, each CSA tile may include multiple RAF circuits.Like the various PEs of the fabric, the RAF circuits may operate in adataflow-style by checking for the availability of input arguments andoutput buffering, if required, before selecting a memory operation toexecute. Unlike some PEs, however, the RAF circuit may be multiplexedamong several co-located memory operations. A multiplexed RAF circuitmay be used to minimize the area overhead of its various subcomponents,e.g., to share the Accelerator Cache Interface (ACI) port (described inmore detail in Section 2.4), shared virtual memory (SVM) supporthardware, mezzanine network interface, and other hardware managementfacilities. However, there are some program characteristics that mayalso motivate this choice. In one embodiment, a (e.g., valid) dataflowgraph is to poll memory in a shared virtual memory system.Memory-latency bound programs, like graph traversals, may utilize manyseparate memory operations to saturate memory bandwidth due tomemory-dependent control flow. Although each RAF may be multiplexed, aCSA may include multiple (e.g., between 8 and 32) RAFs at a tilegranularity to ensure adequate cache bandwidth. RAFs may communicatewith the rest of the fabric via both the local network and/or themezzanine network. Where RAFs are multiplexed, each RAF may beprovisioned with several ports into the local network. These ports mayserve as a minimum latency, highly-deterministic path to memory for useby latency-sensitive or high-bandwidth memory operations. In addition, aRAF may be provisioned with a mezzanine network endpoint, e.g., whichprovides memory access to runtime services and distant user-level memoryaccessors.

FIG. 38 illustrates a request address file (RAF) circuit according toembodiments of the disclosure. In one embodiment, at configuration time,the memory load and store operations that were in a dataflow graph arespecified in registers 3810. The arcs to those memory operations in thedataflow graphs may then be connected to the input queues 3822, 3824,and 3826. The arcs from those memory operations are thus to leavecompletion buffers 3828, 3830, or 3832. Dependency tokens (which may besingle bits) arrive into queues 3818 and 3820. Dependency tokens are toleave from queue 3816. Dependency token counter 3814 may be a compactrepresentation of a queue and track a number of dependency tokens usedfor any given input queue. If the dependency token counters 3814saturate, no additional dependency tokens may be generated for newmemory operations in certain embodiments. Accordingly, a memory orderingcircuit (e.g., a RAF in FIG. 11) may stall scheduling new memoryoperations until the dependency token counters 3814 becomes unsaturated.

As an example for a load, an address arrives into queue 3822 which thescheduler 3812 matches up with a load in 3810. A completion buffer slotfor this load may be assigned in the order the address arrived. Assumingthis particular load in the graph has no dependencies specified, theaddress and completion buffer slot may be sent off to the memory systemby the scheduler (e.g., via memory command 3842). When a result 3841(e.g., payload for a load operation) returns (e.g., to mux 3840 (shownschematically)), it may be stored into the completion buffer slot itspecifies (e.g., as it carried the target slot all along though thememory system). The completion buffer may send results back into localnetwork (e.g., local network 3802, 3804, 3806, or 3808) in the order theaddresses arrived. Stores may be similar except both address and datamay have to arrive before any operation is sent off to the memorysystem. In one embodiment, a TLB manager circuit is to send data (e.g.,a physical to virtual to address mapping) directly to TLB (e.g., forinsertion therein), for example, via dotted two-headed arrow, e.g., asopposed to being sent into RAF buffers (e.g., completion buffers). Oneor more of networks may be a communication network (e.g., packetswitched network and/or circuit switched network). Memory command 3842may be a load or store command. Memory command 3842 may include avirtual address to be accessed. RAF circuit 3800 may include a TLB 3801,e.g., as discussed herein. In one embodiment, TLB 3801 includes one ormore mapping entries 3803 (e.g., from 1 to X, where X is any integer)(e.g., storing a virtual (VA) address to physical address (PA) mapping).Additionally or alternatively, storage 3805 may be included for otherdata, for example, but not limited to, data to indicate which L2 TLB tocheck (e.g., as in FIG. 35) for a miss and/or commands (for example, tocause an (e.g., acknowledgment) message to be sent to a TLB managercircuit) (e.g., for a fill), permission bits: read, write, execute,privilege, and/or an indication that the page has been fractured. Arrow3807 from TLB may represent a connection to an accelerator-cache network(e.g., to access a TLB manger circuit, cache bank, etc.) Note that adouble headed arrow in the figures may not require two-waycommunication, for example, it may indicate one-way communication (e.g.,to or from that component or device). Note that a single headed arrow inthe figures may not require one-way communication, for example, it mayindicate two-way communication (e.g., to and from that component ordevice). Dotted two-headed arrow may be an (e.g., additional) port toallow communications to and/or from a TLB manager circuit, e.g., as inany of the disclosure herein. In one embodiment, TLB 3801 sends arequest (e.g., from arrow 3807) with a virtual address for a miss, and afill with the physical address is returned and entered into TLB 3801(e.g., in corresponding mapping entry of entries 3803). In oneembodiment, request for memory access is sent back into queue (e.g., inone or more of input queues 3822, 3824, and 3826) when there is a missof the virtual address (e.g., ADDR in FIG. 38) in the TLB 3801.

2.7 Floating Point Support

Certain HPC applications are characterized by their need for significantfloating point bandwidth. To meet this need, embodiments of a CSA may beprovisioned with multiple (e.g., between 128 and 256 each) of floatingadd and multiplication PEs, e.g., depending on tile configuration. A CSAmay provide a few other extended precision modes, e.g., to simplify mathlibrary implementation. CSA floating point PEs may support both singleand double precision, but lower precision PEs may support machinelearning workloads. A CSA may provide an order of magnitude morefloating point performance than a processor core. In one embodiment, inaddition to increasing floating point bandwidth, in order to power allof the floating point units, the energy consumed in floating pointoperations is reduced. For example, to reduce energy, a CSA mayselectively gate the low-order bits of the floating point multiplierarray. In examining the behavior of floating point arithmetic, the loworder bits of the multiplication array may often not influence thefinal, rounded product. FIG. 39 illustrates a floating point multiplier3900 partitioned into three regions (the result region, three potentialcarry regions (3902, 3904, 3906), and the gated region) according toembodiments of the disclosure. In certain embodiments, the carry regionis likely to influence the result region and the gated region isunlikely to influence the result region. Considering a gated region of gbits, the maximum carry may be:

${carry}_{g} \leq {\frac{1}{2^{g}}{\sum\limits_{1}^{g}{i\; 2^{i - 1}}}} \leq {{\sum\limits_{1}^{g}\frac{i}{2^{g}}} - {\sum\limits_{1}^{g}\frac{1}{2^{g}}} + 1} \leq {g - 1}$

Given this maximum carry, if the result of the carry region is less than2^(C)-g, where the carry region is c bits wide, then the gated regionmay be ignored since it does not influence the result region. Increasingg means that it is more likely the gated region will be needed, whileincreasing c means that, under random assumption, the gated region willbe unused and may be disabled to avoid energy consumption. Inembodiments of a CSA floating multiplication PE, a two stage pipelinedapproach is utilized in which first the carry region is determined andthen the gated region is determined if it is found to influence theresult. If more information about the context of the multiplication isknown, a CSA more aggressively tune the size of the gated region. InFMA, the multiplication result may be added to an accumulator, which isoften much larger than either of the multiplicands. In this case, theaddend exponent may be observed in advance of multiplication and theCSDA may adjust the gated region accordingly. One embodiment of the CSAincludes a scheme in which a context value, which bounds the minimumresult of a computation, is provided to related multipliers, in order toselect minimum energy gating configurations.

2.8 Runtime Services

In certain embodiment, a CSA includes a heterogeneous and distributedfabric, and consequently, runtime service implementations are toaccommodate several kinds of PEs in a parallel and distributed fashion.Although runtime services in a CSA may be critical, they may beinfrequent relative to user-level computation. Certain implementations,therefore, focus on overlaying services on hardware resources. To meetthese goals, CSA runtime services may be cast as a hierarchy, e.g., witheach layer corresponding to a CSA network. At the tile level, a singleexternal-facing controller may accepts or sends service commands to anassociated core with the CSA tile. A tile-level controller may serve tocoordinate regional controllers at the RAFs, e.g., using the ACInetwork. In turn, regional controllers may coordinate local controllersat certain mezzanine network stops (e.g., network dataflow endpointcircuits). At the lowest level, service specific micro-protocols mayexecute over the local network, e.g., during a special mode controlledthrough the mezzanine controllers. The micro-protocols may permit eachPE (e.g., PE class by type) to interact with the runtime serviceaccording to its own needs. Parallelism is thus implicit in thishierarchical organization, and operations at the lowest levels may occursimultaneously. This parallelism may enables the configuration of a CSAtile in between hundreds of nanoseconds to a few microseconds, e.g.,depending on the configuration size and its location in the memoryhierarchy. Embodiments of the CSA thus leverage properties of dataflowgraphs to improve implementation of each runtime service. One keyobservation is that runtime services may need only to preserve a legallogical view of the dataflow graph, e.g., a state that can be producedthrough some ordering of dataflow operator executions. Services maygenerally not need to guarantee a temporal view of the dataflow graph,e.g., the state of a dataflow graph in a CSA at a specific point intime. This may permit the CSA to conduct most runtime services in adistributed, pipelined, and parallel fashion, e.g., provided that theservice is orchestrated to preserve the logical view of the dataflowgraph. The local configuration micro-protocol may be a packet-basedprotocol overlaid on the local network. Configuration targets may beorganized into a configuration chain, e.g., which is fixed in themicroarchitecture. Fabric (e.g., PE) targets may be configured one at atime, e.g., using a single extra register per target to achievedistributed coordination. To start configuration, a controller may drivean out-of-band signal which places all fabric targets in itsneighborhood into an unconfigured, paused state and swings multiplexorsin the local network to a pre-defined conformation. As the fabric (e.g.,PE) targets are configured, that is they completely receive theirconfiguration packet, they may set their configuration microprotocolregisters, notifying the immediately succeeding target (e.g., PE) thatit may proceed to configure using the subsequent packet. There is nolimitation to the size of a configuration packet, and packets may havedynamically variable length. For example, PEs configuring constantoperands may have a configuration packet that is lengthened to includethe constant field (e.g., X and Y in FIGS. 3B-3C). FIG. 40 illustratesan in-flight configuration of an accelerator 4000 with a plurality ofprocessing elements (e.g., PEs 4002, 4004, 4006, 4008) according toembodiments of the disclosure. Once configured, PEs may execute subjectto dataflow constraints. However, channels involving unconfigured PEsmay be disabled by the microarchitecture, e.g., preventing any undefinedoperations from occurring. These properties allow embodiments of a CSAto initialize and execute in a distributed fashion with no centralizedcontrol whatsoever. From an unconfigured state, configuration may occurcompletely in parallel, e.g., in perhaps as few as 200 nanoseconds.However, due to the distributed initialization of embodiments of a CSA,PEs may become active, for example sending requests to memory, wellbefore the entire fabric is configured. Extraction may proceed in muchthe same way as configuration. The local network may be conformed toextract data from one target at a time, and state bits used to achievedistributed coordination. A CSA may orchestrate extraction to benon-destructive, that is, at the completion of extraction eachextractable target has returned to its starting state. In thisimplementation, all state in the target may be circulated to an egressregister tied to the local network in a scan-like fashion. Althoughin-place extraction may be achieved by introducing new paths at theregister-transfer level (RTL), or using existing lines to provide thesame functionalities with lower overhead. Like configuration,hierarchical extraction is achieved in parallel.

FIG. 41 illustrates a snapshot 4100 of an in-flight, pipelinedextraction according to embodiments of the disclosure. In some use casesof extraction, such as checkpointing, latency may not be a concern solong as fabric throughput is maintained. In these cases, extraction maybe orchestrated in a pipelined fashion. This arrangement, shown in FIG.41, permits most of the fabric to continue executing, while a narrowregion is disabled for extraction. Configuration and extraction may becoordinated and composed to achieve a pipelined context switch.Exceptions may differ qualitatively from configuration and extraction inthat, rather than occurring at a specified time, they arise anywhere inthe fabric at any point during runtime. Thus, in one embodiment, theexception micro-protocol may not be overlaid on the local network, whichis occupied by the user program at runtime, and utilizes its ownnetwork. However, by nature, exceptions are rare and insensitive tolatency and bandwidth. Thus certain embodiments of CSA utilize a packetswitched network to carry exceptions to the local mezzanine stop, e.g.,where they are forwarded up the service hierarchy (e.g., as in FIG. 56).Packets in the local exception network may be extremely small. In manycases, a PE identification (ID) of only two to eight bits suffices as acomplete packet, e.g., since the CSA may create a unique exceptionidentifier as the packet traverses the exception service hierarchy. Sucha scheme may be desirable because it also reduces the area overhead ofproducing exceptions at each PE.

3. Compilation

The ability to compile programs written in high-level languages onto aCSA may be essential for industry adoption. This section gives ahigh-level overview of compilation strategies for embodiments of a CSA.First is a proposal for a CSA software framework that illustrates thedesired properties of an ideal production-quality toolchain. Next, aprototype compiler framework is discussed. A “control-to-dataflowconversion” is then discussed, e.g., to converts ordinary sequentialcontrol-flow code into CSA dataflow assembly code.

3.1 Example Production Framework

FIG. 42 illustrates a compilation toolchain 4200 for an acceleratoraccording to embodiments of the disclosure. This toolchain compileshigh-level languages (such as C, C++, and Fortran) into a combination ofhost code (LLVM) intermediate representation (IR) for the specificregions to be accelerated. The CSA-specific portion of this compilationtoolchain takes LLVM IR as its input, optimizes and compiles this IRinto a CSA assembly, e.g., adding appropriate buffering onlatency-insensitive channels for performance. It then places and routesthe CSA assembly on the hardware fabric, and configures the PEs andnetwork for execution. In one embodiment, the toolchain supports theCSA-specific compilation as a just-in-time (JIT), incorporatingpotential runtime feedback from actual executions. One of the key designcharacteristics of the framework is compilation of (LLVM) IR for theCSA, rather than using a higher-level language as input. While a programwritten in a high-level programming language designed specifically forthe CSA might achieve maximal performance and/or energy efficiency, theadoption of new high-level languages or programming frameworks may beslow and limited in practice because of the difficulty of convertingexisting code bases. Using (LLVM) IR as input enables a wide range ofexisting programs to potentially execute on a CSA, e.g., without theneed to create a new language or significantly modify the front-end ofnew languages that want to run on the CSA.

3.2 Prototype Compiler

FIG. 43 illustrates a compiler 4300 for an accelerator according toembodiments of the disclosure. Compiler 4300 initially focuses onahead-of-time compilation of C and C++ through the (e.g., Clang)front-end. To compile (LLVM) IR, the compiler implements a CSA back-endtarget within LLVM with three main stages. First, the CSA back-endlowers LLVM IR into a target-specific machine instructions for thesequential unit, which implements most CSA operations combined with atraditional RISC-like control-flow architecture (e.g., with branches anda program counter). The sequential unit in the toolchain may serve as auseful aid for both compiler and application developers, since itenables an incremental transformation of a program from control flow(CF) to dataflow (DF), e.g., converting one section of code at a timefrom control-flow to dataflow and validating program correctness. Thesequential unit may also provide a model for handling code that does notfit in the spatial array. Next, the compiler converts these control-flowinstructions into dataflow operators (e.g., code) for the CSA. Thisphase is described later in Section 3.3. Then, the CSA back-end may runits own optimization passes on the dataflow instructions. Finally, thecompiler may dump the instructions in a CSA assembly format. Thisassembly format is taken as input to late-stage tools which place androute the dataflow instructions on the actual CSA hardware.

3.3 Control to Dataflow Conversion

A key portion of the compiler may be implemented in thecontrol-to-dataflow conversion pass, or dataflow conversion pass forshort. This pass takes in a function represented in control flow form,e.g., a control-flow graph (CFG) with sequential machine instructionsoperating on virtual registers, and converts it into a dataflow functionthat is conceptually a graph of dataflow operations (instructions)connected by latency-insensitive channels (LICs). This section gives ahigh-level description of this pass, describing how it conceptuallydeals with memory operations, branches, and loops in certainembodiments.

Straight-Line Code

FIG. 44A illustrates sequential assembly code 4402 according toembodiments of the disclosure. FIG. 44B illustrates dataflow assemblycode 4404 for the sequential assembly code 4402 of FIG. 44A according toembodiments of the disclosure. FIG. 44C illustrates a dataflow graph4406 for the dataflow assembly code 4404 of FIG. 44B for an acceleratoraccording to embodiments of the disclosure.

First, consider the simple case of converting straight-line sequentialcode to dataflow. The dataflow conversion pass may convert a basic blockof sequential code, such as the code shown in FIG. 44A into CSA assemblycode, shown in FIG. 44B. Conceptually, the CSA assembly in FIG. 44Brepresents the dataflow graph shown in FIG. 44C. In this example, eachsequential instruction is translated into a matching CSA assembly. The.lic statements (e.g., for data) declare latency-insensitive channelswhich correspond to the virtual registers in the sequential code (e.g.,Rdata). In practice, the input to the dataflow conversion pass may be innumbered virtual registers. For clarity, however, this section usesdescriptive register names. Note that load and store operations aresupported in the CSA architecture in this embodiment, allowing for manymore programs to run than an architecture supporting only pure dataflow.Since the sequential code input to the compiler is in SSA (singlestaticassignment) form, for a simple basic block, the control-to-dataflow passmay convert each virtual register definition into the production of asingle value on a latency-insensitive channel. The SSA form allowsmultiple uses of a single definition of a virtual register, such as inRdata2). To support this model, the CSA assembly code supports multipleuses of the same LIC (e.g., data2), with the simulator implicitlycreating the necessary copies of the LICs. One key difference betweensequential code and dataflow code is in the treatment of memoryoperations. The code in FIG. 44A is conceptually serial, which meansthat the load32 (ld32) of addr3 should appear to happen after the st32of addr, in case that addr and addr3 addresses overlap.

Branches

To convert programs with multiple basic blocks and conditionals todataflow, the compiler generates special dataflow operators to replacethe branches. More specifically, the compiler uses switch operators tosteer outgoing data at the end of a basic block in the original CFG, andpick operators to select values from the appropriate incoming channel atthe beginning of a basic block. As a concrete example, consider the codeand corresponding dataflow graph in FIGS. 45A-45C, which conditionallycomputes a value of y based on several inputs: a i, x, and n. Aftercomputing the branch condition test, the dataflow code uses a switchoperator (e.g., see FIGS. 3B-3C) steers the value in channel x tochannel xF if test is 0, or channel xT if test is 1. Similarly, a pickoperator (e.g., see FIGS. 3B-3C) is used to send channel yF to y if testis 0, or send channel yT to y if test is 1. In this example, it turnsout that even though the value of a is only used in the true branch ofthe conditional, the CSA is to include a switch operator which steers itto channel aT when test is 1, and consumes (eats) the value when test is0. This latter case is expressed by setting the false output of theswitch to % ign. It may not be correct to simply connect channel adirectly to the true path, because in the cases where execution actuallytakes the false path, this value of “a” will be left over in the graph,leading to incorrect value of a for the next execution of the function.This example highlights the property of control equivalence, a keyproperty in embodiments of correct dataflow conversion.

Control Equivalence:

Consider a single-entry-single-exit control flow graph G with two basicblocks A and B. A and B are control-equivalent if all complete controlflow paths through G visit A and B the same number of times.

LIC Replacement:

In a control flow graph G, suppose an operation in basic block A definesa virtual register x, and an operation in basic block B that uses x.Then a correct control-to-dataflow transformation can replace x with alatency-insensitive channel only if A and B are control equivalent. Thecontrol-equivalence relation partitions the basic blocks of a CFG intostrong control-dependence regions. FIG. 45A illustrates C source code4502 according to embodiments of the disclosure. FIG. 45B illustratesdataflow assembly code 4504 for the C source code 4502 of FIG. 45Aaccording to embodiments of the disclosure. FIG. 45C illustrates adataflow graph 4506 for the dataflow assembly code 4504 of FIG. 45B foran accelerator according to embodiments of the disclosure. In theexample in FIGS. 45A-45C, the basic block before and after theconditionals are control-equivalent to each other, but the basic blocksin the true and false paths are each in their own control dependenceregion. One correct algorithm for converting a CFG to dataflow is tohave the compiler insert (1) switches to compensate for the mismatch inexecution frequency for any values that flow between basic blocks whichare not control equivalent, and (2) picks at the beginning of basicblocks to choose correctly from any incoming values to a basic block.Generating the appropriate control signals for these picks and switchesmay be the key part of dataflow conversion.

Loops

Another important class of CFGs in dataflow conversion are CFGs forsingle-entry-single-exit loops, a common form of loop generated in(LLVM) IR. These loops may be almost acyclic, except for a single backedge from the end of the loop back to a loop header block. The dataflowconversion pass may use same high-level strategy to convert loops as forbranches, e.g., it inserts switches at the end of the loop to directvalues out of the loop (either out the loop exit or around the back-edgeto the beginning of the loop), and inserts picks at the beginning of theloop to choose between initial values entering the loop and valuescoming through the back edge. FIG. 46A illustrates C source code 4602according to embodiments of the disclosure. FIG. 46B illustratesdataflow assembly code 4604 for the C source code 4602 of FIG. 46Aaccording to embodiments of the disclosure. FIG. 46C illustrates adataflow graph 4606 for the dataflow assembly code 4604 of FIG. 46B foran accelerator according to embodiments of the disclosure. FIGS. 46A-46Cshows C and CSA assembly code for an example do-while loop that adds upvalues of a loop induction variable i, as well as the correspondingdataflow graph. For each variable that conceptually cycles around theloop (i and sum), this graph has a corresponding pick/switch pair thatcontrols the flow of these values. Note that this example also uses apick/switch pair to cycle the value of n around the loop, even though nis loop-invariant. This repetition of n enables conversion of n'svirtual register into a LIC, since it matches the execution frequenciesbetween a conceptual definition of n outside the loop and the one ormore uses of n inside the loop. In general, for a correct dataflowconversion, registers that are live-in into a loop are to be repeatedonce for each iteration inside the loop body when the register isconverted into a LIC. Similarly, registers that are updated inside aloop and are live-out from the loop are to be consumed, e.g., with asingle final value sent out of the loop. Loops introduce a wrinkle intothe dataflow conversion process, namely that the control for a pick atthe top of the loop and the switch for the bottom of the loop areoffset. For example, if the loop in FIG. 45A executes three iterationsand exits, the control to picker should be 0, 1, 1, while the control toswitcher should be 1, 1, 0. This control is implemented by starting thepicker channel with an initial extra 0 when the function begins on cycle0 (which is specified in the assembly by the directives .value 0 and.avail 0), and then copying the output switcher into picker. Note thatthe last 0 in switcher restores a final 0 into picker, ensuring that thefinal state of the dataflow graph matches its initial state.

FIG. 47A illustrates a flow diagram 4700 according to embodiments of thedisclosure. Depicted flow 4700 includes decoding an instruction with adecoder of a core of a processor into a decoded instruction 4702;executing the decoded instruction with an execution unit of the core ofthe processor to perform a first operation 4704; receiving an input of adataflow graph comprising a plurality of nodes 4706; overlaying thedataflow graph into a plurality of processing elements of the processorand an interconnect network between the plurality of processing elementsof the processor with each node represented as a dataflow operator inthe plurality of processing elements 4708; and performing a secondoperation of the dataflow graph with the interconnect network and theplurality of processing elements by a respective, incoming operand setarriving at each of the dataflow operators of the plurality ofprocessing elements 4710.

FIG. 47B illustrates a flow diagram 4701 according to embodiments of thedisclosure. Depicted flow 4701 includes receiving an input of a dataflowgraph comprising a plurality of nodes 4703; and overlaying the dataflowgraph into a plurality of processing elements of a processor, a datapath network between the plurality of processing elements, and a flowcontrol path network between the plurality of processing elements witheach node represented as a dataflow operator in the plurality ofprocessing elements 4705.

In one embodiment, the core writes a command into a memory queue and aCSA (e.g., the plurality of processing elements) monitors the memoryqueue and begins executing when the command is read. In one embodiment,the core executes a first part of a program and a CSA (e.g., theplurality of processing elements) executes a second part of the program.In one embodiment, the core does other work while the CSA is executingits operations.

4. CSA Advantages

In certain embodiments, the CSA architecture and microarchitectureprovides profound energy, performance, and usability advantages overroadmap processor architectures and FPGAs. In this section, thesearchitectures are compared to embodiments of the CSA and highlights thesuperiority of CSA in accelerating parallel dataflow graphs relative toeach.

4.1 Processors

FIG. 48 illustrates a throughput versus energy per operation graph 4800according to embodiments of the disclosure. As shown in FIG. 48, smallcores are generally more energy efficient than large cores, and, in someworkloads, this advantage may be translated to absolute performancethrough higher core counts. The CSA microarchitecture follows theseobservations to their conclusion and removes (e.g., most) energy-hungrycontrol structures associated with von Neumann architectures, includingmost of the instruction-side microarchitecture. By removing theseoverheads and implementing simple, single operation PEs, embodiments ofa CSA obtains a dense, efficient spatial array. Unlike small cores,which are usually quite serial, a CSA may gang its PEs together, e.g.,via the circuit switched local network, to form explicitly parallelaggregate dataflow graphs. The result is performance in not onlyparallel applications, but also serial applications as well. Unlikecores, which may pay dearly for performance in terms area and energy, aCSA is already parallel in its native execution model. In certainembodiments, a CSA neither requires speculation to increase performancenor does it need to repeatedly re-extract parallelism from a sequentialprogram representation, thereby avoiding two of the main energy taxes invon Neumann architectures. Most structures in embodiments of a CSA aredistributed, small, and energy efficient, as opposed to the centralized,bulky, energy hungry structures found in cores. Consider the case ofregisters in the CSA: each PE may have a few (e.g., 10 or less) storageregisters. Taken individually, these registers may be more efficientthat traditional register files. In aggregate, these registers mayprovide the effect of a large, in-fabric register file. As a result,embodiments of a CSA avoids most of stack spills and fills incurred byclassical architectures, while using much less energy per state access.Of course, applications may still access memory. In embodiments of aCSA, memory access request and response are architecturally decoupled,enabling workloads to sustain many more outstanding memory accesses perunit of area and energy. This property yields substantially higherperformance for cache-bound workloads and reduces the area and energyneeded to saturate main memory in memory-bound workloads. Embodiments ofa CSA expose new forms of energy efficiency which are unique to non-vonNeumann architectures. One consequence of executing a single operation(e.g., instruction) at a (e.g., most) PEs is reduced operand entropy. Inthe case of an increment operation, each execution may result in ahandful of circuit-level toggles and little energy consumption, a caseexamined in detail in Section 5.2. In contrast, von Neumannarchitectures are multiplexed, resulting in large numbers of bittransitions. The asynchronous style of embodiments of a CSA also enablesmicroarchitectural optimizations, such as the floating pointoptimizations described in Section 2.7 that are difficult to realize intightly scheduled core pipelines. Because PEs may be relatively simpleand their behavior in a particular dataflow graph be statically known,clock gating and power gating techniques may be applied more effectivelythan in coarser architectures. The graph-execution style, small size,and malleability of embodiments of CSA PEs and the network togetherenable the expression many kinds of parallelism: instruction, data,pipeline, vector, memory, thread, and task parallelism may all beimplemented. For example, in embodiments of a CSA, one application mayuse arithmetic units to provide a high degree of address bandwidth,while another application may use those same units for computation. Inmany cases, multiple kinds of parallelism may be combined to achieveeven more performance. Many key HPC operations may be both replicatedand pipelined, resulting in orders-of-magnitude performance gains. Incontrast, von Neumann-style cores typically optimize for one style ofparallelism, carefully chosen by the architects, resulting in a failureto capture all important application kernels. Just as embodiments of aCSA expose and facilitates many forms of parallelism, it does notmandate a particular form of parallelism, or, worse, a particularsubroutine be present in an application in order to benefit from theCSA. Many applications, including single-stream applications, may obtainboth performance and energy benefits from embodiments of a CSA, e.g.,even when compiled without modification. This reverses the long trend ofrequiring significant programmer effort to obtain a substantialperformance gain in singlestream applications. Indeed, in someapplications, embodiments of a CSA obtain more performance fromfunctionally equivalent, but less “modern” codes than from theirconvoluted, contemporary cousins which have been tortured to targetvector instructions.

4.2 Comparison of CSA Embodiments and FGPAs

The choice of dataflow operators as the fundamental architecture ofembodiments of a CSA differentiates those CSAs from a FGPA, andparticularly the CSA is as superior accelerator for HPC dataflow graphsarising from traditional programming languages. Dataflow operators arefundamentally asynchronous. This enables embodiments of a CSA not onlyto have great freedom of implementation in the microarchitecture, but italso enables them to simply and succinctly accommodate abstractarchitectural concepts. For example, embodiments of a CSA naturallyaccommodate many memory microarchitectures, which are essentiallyasynchronous, with a simple load-store interface. One need only examinean FPGA DRAM controller to appreciate the difference in complexity.Embodiments of a CSA also leverage asynchrony to provide faster andmore-fully-featured runtime services like configuration and extraction,which are believed to be four to six orders of magnitude faster than anFPGA. By narrowing the architectural interface, embodiments of a CSAprovide control over most timing paths at the microarchitectural level.This allows embodiments of a CSA to operate at a much higher frequencythan the more general control mechanism offered in a FPGA. Similarly,clock and reset, which may be architecturally fundamental to FPGAs, aremicroarchitectural in the CSA, e.g., obviating the need to support themas programmable entities. Dataflow operators may be, for the most part,coarse-grained. By only dealing in coarse operators, embodiments of aCSA improve both the density of the fabric and its energy consumption:CSA executes operations directly rather than emulating them with look-uptables. A second consequence of coarseness is a simplification of theplace and route problem. CSA dataflow graphs are many orders ofmagnitude smaller than FPGA net-lists and place and route time arecommensurately reduced in embodiments of a CSA. The significantdifferences between embodiments of a CSA and a FPGA make the CSAsuperior as an accelerator, e.g., for dataflow graphs arising fromtraditional programming languages.

5. Evaluation

The CSA is a novel computer architecture with the potential to provideenormous performance and energy advantages relative to roadmapprocessors. Consider the case of computing a single strided address forwalking across an array. This case may be important in HPC applications,e.g., which spend significant integer effort in computing addressoffsets. In address computation, and especially strided addresscomputation, one argument is constant and the other varies only slightlyper computation. Thus, only a handful of bits per cycle toggle in themajority of cases. Indeed, it may be shown, using a derivation similarto the bound on floating point carry bits described in Section 2.7, thatless than two bits of input toggle per computation in average for astride calculation, reducing energy by 50% over a random toggledistribution. Were a time-multiplexed approach used, much of this energysavings may be lost. In one embodiment, the CSA achieves approximately3× energy efficiency over a core while delivering an 8× performancegain. The parallelism gains achieved by embodiments of a CSA may resultin reduced program run times, yielding a proportionate, substantialreduction in leakage energy. At the PE level, embodiments of a CSA areextremely energy efficient. A second important question for the CSA iswhether the CSA consumes a reasonable amount of energy at the tilelevel. Since embodiments of a CSA are capable of exercising everyfloating point PE in the fabric at every cycle, it serves as areasonable upper bound for energy and power consumption, e.g., such thatmost of the energy goes into floating point multiply and add.

6. Further CSA Details

This section discusses further details for configuration and exceptionhandling.

6.1 Microarchitecture for Configuring a CSA

This section discloses examples of how to configure a CSA (e.g.,fabric), how to achieve this configuration quickly, and how to minimizethe resource overhead of configuration. Configuring the fabric quicklymay be of preeminent importance in accelerating small portions of alarger algorithm, and consequently in broadening the applicability of aCSA. The section further discloses features that allow embodiments of aCSA to be programmed with configurations of different length.

Embodiments of a CSA (e.g., fabric) may differ from traditional cores inthat they make use of a configuration step in which (e.g., large) partsof the fabric are loaded with program configuration in advance ofprogram execution. An advantage of static configuration may be that verylittle energy is spent at runtime on the configuration, e.g., as opposedto sequential cores which spend energy fetching configurationinformation (an instruction) nearly every cycle. The previousdisadvantage of configuration is that it was a coarse-grained step witha potentially large latency, which places an under-bound on the size ofprogram that can be accelerated in the fabric due to the cost of contextswitching. This disclosure describes a scalable microarchitecture forrapidly configuring a spatial array in a distributed fashion, e.g., thatavoids the previous disadvantages.

As discussed above, a CSA may include light-weight processing elementsconnected by an inter-PE network. Programs, viewed as control-dataflowgraphs, are then mapped onto the architecture by configuring theconfigurable fabric elements (CFEs), for example PEs and theinterconnect (fabric) networks. Generally, PEs may be configured asdataflow operators and once all input operands arrive at the PE, someoperation occurs, and the results are forwarded to another PE or PEs forconsumption or output. PEs may communicate over dedicated virtualcircuits which are formed by statically configuring the circuit switchedcommunications network. These virtual circuits may be flow controlledand fully back-pressured, e.g., such that PEs will stall if either thesource has no data or destination is full. At runtime, data may flowthrough the PEs implementing the mapped algorithm. For example, data maybe streamed in from memory, through the fabric, and then back out tomemory. Such a spatial architecture may achieve remarkable performanceefficiency relative to traditional multicore processors: compute, in theform of PEs, may be simpler and more numerous than larger cores andcommunications may be direct, as opposed to an extension of the memorysystem.

Embodiments of a CSA may not utilize (e.g., software controlled) packetswitching, e.g., packet switching that requires significant softwareassistance to realize, which slows configuration. Embodiments of a CSAinclude out-of-band signaling in the network (e.g., of only 2-3 bits,depending on the feature set supported) and a fixed configurationtopology to avoid the need for significant software support.

One key difference between embodiments of a CSA and the approach used inFPGAs is that a CSA approach may use a wide data word, is distributed,and includes mechanisms to fetch program data directly from memory.Embodiments of a CSA may not utilize JTAG-style single bitcommunications in the interest of area efficiency, e.g., as that mayrequire milliseconds to completely configure a large FPGA fabric.

Embodiments of a CSA include a distributed configuration protocol andmicroarchitecture to support this protocol. Initially, configurationstate may reside in memory. Multiple (e.g., distributed) localconfiguration controllers (boxes) (LCCs) may stream portions of theoverall program into their local region of the spatial fabric, e.g.,using a combination of a small set of control signals and thefabric-provided network. State elements may be used at each CFE to formconfiguration chains, e.g., allowing individual CFEs to self-programwithout global addressing.

Embodiments of a CSA include specific hardware support for the formationof configuration chains, e.g., not software establishing these chainsdynamically at the cost of increasing configuration time. Embodiments ofa CSA are not purely packet switched and do include extra out-of-bandcontrol wires (e.g., control is not sent through the data path requiringextra cycles to strobe this information and reserialize thisinformation). Embodiments of a CSA decreases configuration latency byfixing the configuration ordering and by providing explicit out-of-bandcontrol (e.g., by at least a factor of two), while not significantlyincreasing network complexity.

Embodiments of a CSA do not use a serial mechanism for configuration inwhich data is streamed bit by bit into the fabric using a JTAG-likeprotocol. Embodiments of a CSA utilize a coarse-grained fabric approach.In certain embodiments, adding a few control wires or state elements toa 64 or 32-bit-oriented CSA fabric has a lower cost relative to addingthose same control mechanisms to a 4 or 6 bit fabric.

FIG. 49 illustrates an accelerator tile 4900 comprising an array ofprocessing elements (PE) and a local configuration controller (4902,4906) according to embodiments of the disclosure. Each PE, each networkcontroller (e.g., network dataflow endpoint circuit), and each switchmay be a configurable fabric elements (CFEs), e.g., which are configured(e.g., programmed) by embodiments of the CSA architecture.

Embodiments of a CSA include hardware that provides for efficient,distributed, low-latency configuration of a heterogeneous spatialfabric. This may be achieved according to four techniques. First, ahardware entity, the local configuration controller (LCC) is utilized,for example, as in FIGS. 49-51. An LCC may fetch a stream ofconfiguration information from (e.g., virtual) memory. Second, aconfiguration data path may be included, e.g., that is as wide as thenative width of the PE fabric and which may be overlaid on top of the PEfabric. Third, new control signals may be received into the PE fabricwhich orchestrate the configuration process. Fourth, state elements maybe located (e.g., in a register) at each configurable endpoint whichtrack the status of adjacent CFEs, allowing each CFE to unambiguouslyself-configure without extra control signals. These fourmicroarchitectural features may allow a CSA to configure chains of itsCFEs. To obtain low configuration latency, the configuration may bepartitioned by building many LCCs and CFE chains. At configuration time,these may operate independently to load the fabric in parallel, e.g.,dramatically reducing latency. As a result of these combinations,fabrics configured using embodiments of a CSA architecture, may becompletely configured (e.g., in hundreds of nanoseconds). In thefollowing, the detailed the operation of the various components ofembodiments of a CSA configuration network are disclosed.

FIGS. 50A-50C illustrate a local configuration controller 5002configuring a data path network according to embodiments of thedisclosure. Depicted network includes a plurality of multiplexers (e.g.,multiplexers 5006, 5008, 5010) that may be configured (e.g., via theirrespective control signals) to connect one or more data paths (e.g.,from PEs) together. FIG. 50A illustrates the network 5000 (e.g., fabric)configured (e.g., set) for some previous operation or program. FIG. 50Billustrates the local configuration controller 5002 (e.g., including anetwork interface circuit 5004 to send and/or receive signals) strobinga configuration signal and the local network is set to a defaultconfiguration (e.g., as depicted) that allows the LCC to sendconfiguration data to all configurable fabric elements (CFEs), e.g.,muxes. FIG. 50C illustrates the LCC strobing configuration informationacross the network, configuring CFEs in a predetermined (e.g.,silicon-defined) sequence. In one embodiment, when CFEs are configuredthey may begin operation immediately. In another embodiments, the CFEswait to begin operation until the fabric has been completely configured(e.g., as signaled by configuration terminator (e.g., configurationterminator 5204 and configuration terminator 5208 in FIG. 52) for eachlocal configuration controller). In one embodiment, the LCC obtainscontrol over the network fabric by sending a special message, or drivinga signal. It then strobes configuration data (e.g., over a period ofmany cycles) to the CFEs in the fabric. In these figures, themultiplexor networks are analogues of the “Switch” shown in certainFigures (e.g., FIG. 6).

Local Configuration Controller

FIG. 51 illustrates a (e.g., local) configuration controller 5102according to embodiments of the disclosure. A local configurationcontroller (LCC) may be the hardware entity which is responsible forloading the local portions (e.g., in a subset of a tile or otherwise) ofthe fabric program, interpreting these program portions, and thenloading these program portions into the fabric by driving theappropriate protocol on the various configuration wires. In thiscapacity, the LCC may be a special-purpose, sequential microcontroller.

LCC operation may begin when it receives a pointer to a code segment.Depending on the LCB microarchitecture, this pointer (e.g., stored inpointer register 5106) may come either over a network (e.g., from withinthe CSA (fabric) itself) or through a memory system access to the LCC.When it receives such a pointer, the LCC optionally drains relevantstate from its portion of the fabric for context storage, and thenproceeds to immediately reconfigure the portion of the fabric for whichit is responsible. The program loaded by the LCC may be a combination ofconfiguration data for the fabric and control commands for the LCC,e.g., which are lightly encoded. As the LCC streams in the programportion, it may interprets the program as a command stream and performthe appropriate encoded action to configure (e.g., load) the fabric.

Two different microarchitectures for the LCC are shown in FIG. 49, e.g.,with one or both being utilized in a CSA. The first places the LCC 4902at the memory interface. In this case, the LCC may make direct requeststo the memory system to load data. In the second case the LCC 4906 isplaced on a memory network, in which it may make requests to the memoryonly indirectly. In both cases, the logical operation of the LCB isunchanged. In one embodiment, an LCCs is informed of the program toload, for example, by a set of (e.g., OS-visible)control-status-registers which will be used to inform individual LCCs ofnew program pointers, etc.

Extra Out-Of-Band Control Channels (e.g., Wires)

In certain embodiments, configuration relies on 2-8 extra, out-of-bandcontrol channels to improve configuration speed, as defined below. Forexample, configuration controller 5102 may include the following controlchannels, e.g., CFG_START control channel 5108, CFG_VALID controlchannel 5110, and CFG_DONE control channel 5112, with examples of eachdiscussed in Table 2 below.

TABLE 2 Control Channels CFG_START Asserted at beginning ofconfiguration. Sets configuration state at each CFE and sets theconfiguration bus. CFG_VALID Denotes validity of values on configurationbus. CFG_DONE Optional. Denotes completion of the configuration of aparticular CFE. This allows configuration to be short circuited in casea CFE does not require additional configuration

Generally, the handling of configuration information may be left to theimplementer of a particular CFE. For example, a selectable function CFEmay have a provision for setting registers using an existing data path,while a fixed function CFE might simply set a configuration register.

Due to long wire delays when programming a large set of CFEs, theCFG_VALID signal may be treated as a clock/latch enable for CFEcomponents. Since this signal is used as a clock, in one embodiment theduty cycle of the line is at most 50%. As a result, configurationthroughput is approximately halved. Optionally, a second CFG_VALIDsignal may be added to enable continuous programming.

In one embodiment, only CFG_START is strictly communicated on anindependent coupling (e.g., wire), for example, CFG_VALID and CFG_DONEmay be overlaid on top of other network couplings.

Reuse of Network Resources

To reduce the overhead of configuration, certain embodiments of a CSAmake use of existing network infrastructure to communicate configurationdata. A LCC may make use of both a chip-level memory hierarchy and afabric-level communications networks to move data from storage into thefabric. As a result, in certain embodiments of a CSA, the configurationinfrastructure adds no more than 2% to the overall fabric area andpower.

Reuse of network resources in certain embodiments of a CSA may cause anetwork to have some hardware support for a configuration mechanism.Circuit switched networks of embodiments of a CSA cause an LCC to settheir multiplexors in a specific way for configuration when the‘CFG_START’ signal is asserted. Packet switched networks do not requireextension, although LCC endpoints (e.g., configuration terminators) usea specific address in the packet switched network. Network reuse isoptional, and some embodiments may find dedicated configuration buses tobe more convenient.

Per CFE State

Each CFE may maintain a bit denoting whether or not it has beenconfigured (see, e.g., FIG. 40). This bit may be de-asserted when theconfiguration start signal is driven, and then asserted once theparticular CFE has been configured. In one configuration protocol, CFEsare arranged to form chains with the CFE configuration state bitdetermining the topology of the chain. A CFE may read the configurationstate bit of the immediately adjacent CFE. If this adjacent CFE isconfigured and the current CFE is not configured, the CFE may determinethat any current configuration data is targeted at the current CFE. Whenthe ‘CFG_DONE’ signal is asserted, the CFE may set its configurationbit, e.g., enabling upstream CFEs to configure. As a base case to theconfiguration process, a configuration terminator (e.g., configurationterminator 4904 for LCC 4902 or configuration terminator 4908 for LCC4906 in FIG. 49) which asserts that it is configured may be included atthe end of a chain.

Internal to the CFE, this bit may be used to drive flow control readysignals. For example, when the configuration bit is de-asserted, networkcontrol signals may automatically be clamped to a values that preventdata from flowing, while, within PEs, no operations or other actionswill be scheduled.

Dealing with High-Delay Configuration Paths

One embodiment of an LCC may drive a signal over a long distance, e.g.,through many multiplexors and with many loads. Thus, it may be difficultfor a signal to arrive at a distant CFE within a short clock cycle. Incertain embodiments, configuration signals are at some division (e.g.,fraction of) of the main (e.g., CSA) clock frequency to ensure digitaltiming discipline at configuration. Clock division may be utilized in anout-of-band signaling protocol, and does not require any modification ofthe main clock tree.

Ensuring Consistent Fabric Behavior During Configuration

Since certain configuration schemes are distributed and havenon-deterministic timing due to program and memory effects, differentportions of the fabric may be configured at different times. As aresult, certain embodiments of a CSA provide mechanisms to preventinconsistent operation among configured and unconfigured CFEs.Generally, consistency is viewed as a property required of andmaintained by CFEs themselves, e.g., using the internal CFE state. Forexample, when a CFE is in an unconfigured state, it may claim that itsinput buffers are full, and that its output is invalid. When configured,these values will be set to the true state of the buffers. As enough ofthe fabric comes out of configuration, these techniques may permit it tobegin operation. This has the effect of further reducing contextswitching latency, e.g., if long-latency memory requests are issuedearly.

Variable-Width Configuration

Different CFEs may have different configuration word widths. For smallerCFE configuration words, implementers may balance delay by equitablyassigning CFE configuration loads across the network wires. To balanceloading on network wires, one option is to assign configuration bits todifferent portions of network wires to limit the net delay on any onewire. Wide data words may be handled by usingserialization/deserialization techniques. These decisions may be takenon a per-fabric basis to optimize the behavior of a specific CSA (e.g.,fabric). Network controller (e.g., one or more of network controller4910 and network controller 4912 may communicate with each domain (e.g.,subset) of the CSA (e.g., fabric), for example, to send configurationinformation to one or more LCCs. Network controller may be part of acommunications network (e.g., separate from circuit switched network).Network controller may include a network dataflow endpoint circuit.

6.2 Microarchitecture for Low Latency Configuration of a CSA and forTimely Fetching of Configuration Data for a CSA

Embodiments of a CSA may be an energy-efficient and high-performancemeans of accelerating user applications. When considering whether aprogram (e.g., a dataflow graph thereof) may be successfully acceleratedby an accelerator, both the time to configure the accelerator and thetime to run the program may be considered. If the run time is short,then the configuration time may play a large role in determiningsuccessful acceleration. Therefore, to maximize the domain ofaccelerable programs, in some embodiments the configuration time is madeas short as possible. One or more configuration caches may be includesin a CSA, e.g., such that the high bandwidth, low-latency store enablesrapid reconfiguration. Next is a description of several embodiments of aconfiguration cache.

In one embodiment, during configuration, the configuration hardware(e.g., LCC) optionally accesses the configuration cache to obtain newconfiguration information. The configuration cache may operate either asa traditional address based cache, or in an OS managed mode, in whichconfigurations are stored in the local address space and addressed byreference to that address space. If configuration state is located inthe cache, then no requests to the backing store are to be made incertain embodiments. In certain embodiments, this configuration cache isseparate from any (e.g., lower-level) shared cache in the memoryhierarchy.

FIG. 52 illustrates an accelerator tile 5200 comprising an array ofprocessing elements, a configuration cache (e.g., 5218 or 5220), and alocal configuration controller (e.g., 5202 or 5206) according toembodiments of the disclosure. In one embodiment, configuration cache5214 is co-located with local configuration controller 5202. In oneembodiment, configuration cache 5218 is located in the configurationdomain of local configuration controller 5206, e.g., with a first domainending at configuration terminator 5204 and a second domain ending atconfiguration terminator 5208). A configuration cache may allow a localconfiguration controller may refer to the configuration cache duringconfiguration, e.g., in the hope of obtaining configuration state withlower latency than a reference to memory. A configuration cache(storage) may either be dedicated or may be accessed as a configurationmode of an in-fabric storage element, e.g., local cache 5216.

Caching Modes

-   -   1. Demand Caching—In this mode, the configuration cache operates        as a true cache. The configuration controller issues        address-based requests, which are checked against tags in the        cache. Misses are loaded into the cache and then may be        re-referenced during future reprogramming.    -   2. In-Fabric Storage (Scratchpad) Caching—In this mode the        configuration cache receives a reference to a configuration        sequence in its own, small address space, rather than the larger        address space of the host. This may improve memory density since        the portion of cache used to store tags may instead be used to        store configuration.

In certain embodiments, a configuration cache may have the configurationdata pre-loaded into it, e.g., either by external direction or internaldirection. This may allow reduction in the latency to load programs.Certain embodiments herein provide for an interface to a configurationcache which permits the loading of new configuration state into thecache, e.g., even if a configuration is running in the fabric already.The initiation of this load may occur from either an internal orexternal source. Embodiments of a pre-loading mechanism further reducelatency by removing the latency of cache loading from the configurationpath.

Pre Fetching Modes

-   -   1. Explicit Prefetching—A configuration path is augmented with a        new command, ConfigurationCachePrefetch. Instead of programming        the fabric, this command simply cause a load of the relevant        program configuration into a configuration cache, without        programming the fabric. Since this mechanism piggybacks on the        existing configuration infrastructure, it is exposed both within        the fabric and externally, e.g., to cores and other entities        accessing the memory space.    -   2. Implicit prefetching—A global configuration controller may        maintain a prefetch predictor, and use this to initiate the        explicit prefetching to a configuration cache, e.g., in an        automated fashion.

6.3 Hardware for Rapid Reconfiguration of a CSA in Response to anException

Certain embodiments of a CSA (e.g., a spatial fabric) include largeamounts of instruction and configuration state, e.g., which is largelystatic during the operation of the CSA. Thus, the configuration statemay be vulnerable to soft errors. Rapid and error-free recovery of thesesoft errors may be critical to the long-term reliability and performanceof spatial systems.

Certain embodiments herein provide for a rapid configuration recoveryloop, e.g., in which configuration errors are detected and portions ofthe fabric immediately reconfigured. Certain embodiments herein includea configuration controller, e.g., with reliability, availability, andserviceability (RAS) reprogramming features. Certain embodiments of CSAinclude circuitry for high-speed configuration, error reporting, andparity checking within the spatial fabric. Using a combination of thesethree features, and optionally, a configuration cache, aconfiguration/exception handling circuit may recover from soft errors inconfiguration. When detected, soft errors may be conveyed to aconfiguration cache which initiates an immediate reconfiguration of(e.g., that portion of) the fabric. Certain embodiments provide for adedicated reconfiguration circuit, e.g., which is faster than anysolution that would be indirectly implemented in the fabric. In certainembodiments, co-located exception and configuration circuit cooperatesto reload the fabric on configuration error detection.

FIG. 53 illustrates an accelerator tile 5300 comprising an array ofprocessing elements and a configuration and exception handlingcontroller (5302, 5306) with a reconfiguration circuit (5318, 5322)according to embodiments of the disclosure. In one embodiment, when a PEdetects a configuration error through its local RAS features, it sends a(e.g., configuration error or reconfiguration error) message by itsexception generator to the configuration and exception handlingcontroller (e.g., 5302 or 5306). On receipt of this message, theconfiguration and exception handling controller (e.g., 5302 or 5306)initiates the co-located reconfiguration circuit (e.g., 5318 or 5322,respectively) to reload configuration state. The configurationmicroarchitecture proceeds and reloads (e.g., only) configurationsstate, and in certain embodiments, only the configuration state for thePE reporting the RAS error. Upon completion of reconfiguration, thefabric may resume normal operation. To decrease latency, theconfiguration state used by the configuration and exception handlingcontroller (e.g., 5302 or 5306) may be sourced from a configurationcache. As a base case to the configuration or reconfiguration process, aconfiguration terminator (e.g., configuration terminator 5304 forconfiguration and exception handling controller 5302 or configurationterminator 5308 for configuration and exception handling controller5306) in FIG. 53) which asserts that it is configured (or reconfigures)may be included at the end of a chain.

FIG. 54 illustrates a reconfiguration circuit 5418 according toembodiments of the disclosure. Reconfiguration circuit 5418 includes aconfiguration state register 5420 to store the configuration state (or apointer thereto).

7.4 Hardware for Fabric-Initiated Reconfiguration of a CSA

Some portions of an application targeting a CSA (e.g., spatial array)may be run infrequently or may be mutually exclusive with other parts ofthe program. To save area, to improve performance, and/or reduce power,it may be useful to time multiplex portions of the spatial fabric amongseveral different parts of the program dataflow graph. Certainembodiments herein include an interface by which a CSA (e.g., via thespatial program) may request that part of the fabric be reprogrammed.This may enable the CSA to dynamically change itself according todynamic control flow. Certain embodiments herein allow for fabricinitiated reconfiguration (e.g., reprogramming). Certain embodimentsherein provide for a set of interfaces for triggering configuration fromwithin the fabric. In some embodiments, a PE issues a reconfigurationrequest based on some decision in the program dataflow graph. Thisrequest may travel a network to our new configuration interface, whereit triggers reconfiguration. Once reconfiguration is completed, amessage may optionally be returned notifying of the completion. Certainembodiments of a CSA thus provide for a program (e.g., dataflow graph)directed reconfiguration capability.

FIG. 55 illustrates an accelerator tile 5500 comprising an array ofprocessing elements and a configuration and exception handlingcontroller 5506 with a reconfiguration circuit 5518 according toembodiments of the disclosure. Here, a portion of the fabric issues arequest for (re)configuration to a configuration domain, e.g., ofconfiguration and exception handling controller 5506 and/orreconfiguration circuit 5518. The domain (re)configures itself, and whenthe request has been satisfied, the configuration and exception handlingcontroller 5506 and/or reconfiguration circuit 5518 issues a response tothe fabric, to notify the fabric that (re)configuration is complete. Inone embodiment, configuration and exception handling controller 5506and/or reconfiguration circuit 5518 disables communication during thetime that (re)configuration is ongoing, so the program has noconsistency issues during operation.

Configuration Modes

Configure-by-address—In this mode, the fabric makes a direct request toload configuration data from a particular address.

Configure-by-reference—In this mode the fabric makes a request to load anew configuration, e.g., by a pre-determined reference ID. This maysimplify the determination of the code to load, since the location ofthe code has been abstracted.

Configuring Multiple Domains

A CSA may include a higher-level configuration controller to support amulticast mechanism to cast (e.g., via network indicated by the dottedbox) configuration requests to multiple (e.g., distributed or local)configuration controllers. This may enable a single configurationrequest to be replicated across larger portions of the fabric, e.g.,triggering a broad reconfiguration.

6.5 Exception Aggregators

Certain embodiments of a CSA may also experience an exception (e.g.,exceptional condition), for example, floating point underflow. Whenthese conditions occur, a special handlers may be invoked to eithercorrect the program or to terminate it. Certain embodiments hereinprovide for a system-level architecture for handling exceptions inspatial fabrics. Since certain spatial fabrics emphasize areaefficiency, embodiments herein minimize total area while providing ageneral exception mechanism. Certain embodiments herein provides a lowarea means of signaling exceptional conditions occurring in within a CSA(e.g., a spatial array). Certain embodiments herein provide an interfaceand signaling protocol for conveying such exceptions, as well as aPE-level exception semantics. Certain embodiments herein are dedicatedexception handling capabilities, e.g., and do not require explicithandling by the programmer.

One embodiments of a CSA exception architecture consists of fourportions, e.g., shown in FIGS. 56-57. These portions may be arranged ina hierarchy, in which exceptions flow from the producer, and eventuallyup to the tile-level exception aggregator (e.g., handler), which mayrendezvous with an exception servicer, e.g., of a core. The fourportions may be:

1. PE Exception Generator

2. Local Exception Network

3. Mezzanine Exception Aggregator

4. Tile-Level Exception Aggregator

FIG. 56 illustrates an accelerator tile 5600 comprising an array ofprocessing elements and a mezzanine exception aggregator 5602 coupled toa tile-level exception aggregator 5604 according to embodiments of thedisclosure. FIG. 57 illustrates a processing element 5700 with anexception generator 5744 according to embodiments of the disclosure.

PE Exception Generator

Processing element 5700 may include processing element 900 from FIG. 9,for example, with similar numbers being similar components, e.g., localnetwork 902 and local network 5702. Additional network 5713 (e.g.,channel) may be an exception network. A PE may implement an interface toan exception network (e.g., exception network 5713 (e.g., channel) onFIG. 57). For example, FIG. 57 shows the microarchitecture of such aninterface, wherein the PE has an exception generator 5744 (e.g.,initiate an exception finite state machine (FSM) 5740 to strobe anexception packet (e.g., BOXID 5742) out on to the exception network.BOXID 5742 may be a unique identifier for an exception producing entity(e.g., a PE or box) within a local exception network. When an exceptionis detected, exception generator 5744 senses the exception network andstrobes out the BOXID when the network is found to be free. Exceptionsmay be caused by many conditions, for example, but not limited to,arithmetic error, failed ECC check on state, etc. however, it may alsobe that an exception dataflow operation is introduced, with the idea ofsupport constructs like breakpoints.

The initiation of the exception may either occur explicitly, by theexecution of a programmer supplied instruction, or implicitly when ahardened error condition (e.g., a floating point underflow) is detected.Upon an exception, the PE 5700 may enter a waiting state, in which itwaits to be serviced by the eventual exception handler, e.g., externalto the PE 5700. The contents of the exception packet depend on theimplementation of the particular PE, as described below.

Local Exception Network

A (e.g., local) exception network steers exception packets from PE 5700to the mezzanine exception network. Exception network (e.g., 5713) maybe a serial, packet switched network consisting of a (e.g., single)control wire and one or more data wires, e.g., organized in a ring ortree topology, e.g., for a subset of PEs. Each PE may have a (e.g.,ring) stop in the (e.g., local) exception network, e.g., where it canarbitrate to inject messages into the exception network.

PE endpoints needing to inject an exception packet may observe theirlocal exception network egress point. If the control signal indicatesbusy, the PE is to wait to commence inject its packet. If the network isnot busy, that is, the downstream stop has no packet to forward, thenthe PE will proceed commence injection.

Network packets may be of variable or fixed length. Each packet maybegin with a fixed length header field identifying the source PE of thepacket. This may be followed by a variable number of PE-specific fieldcontaining information, for example, including error codes, data values,or other useful status information.

Mezzanine Exception Aggregator

The mezzanine exception aggregator 5604 is responsible for assemblinglocal exception network into larger packets and sending them to thetile-level exception aggregator 5602. The mezzanine exception aggregator5604 may pre-pend the local exception packet with its own unique ID,e.g., ensuring that exception messages are unambiguous. The mezzanineexception aggregator 5604 may interface to a special exception-onlyvirtual channel in the mezzanine network, e.g., ensuring thedeadlock-freedom of exceptions.

The mezzanine exception aggregator 5604 may also be able to directlyservice certain classes of exception. For example, a configurationrequest from the fabric may be served out of the mezzanine network usingcaches local to the mezzanine network stop.

Tile-Level Exception Aggregator

The final stage of the exception system is the tile-level exceptionaggregator 5602. The tile-level exception aggregator 5602 is responsiblefor collecting exceptions from the various mezzanine-level exceptionaggregators (e.g., 5604) and forwarding them to the appropriateservicing hardware (e.g., core). As such, the tile-level exceptionaggregator 5602 may include some internal tables and controller toassociate particular messages with handler routines. These tables may beindexed either directly or with a small state machine in order to steerparticular exceptions.

Like the mezzanine exception aggregator, the tile-level exceptionaggregator may service some exception requests. For example, it mayinitiate the reprogramming of a large portion of the PE fabric inresponse to a specific exception.

6.6 Extraction Controllers

Certain embodiments of a CSA include an extraction controller(s) toextract data from the fabric. The below discusses embodiments of how toachieve this extraction quickly and how to minimize the resourceoverhead of data extraction. Data extraction may be utilized for suchcritical tasks as exception handling and context switching. Certainembodiments herein extract data from a heterogeneous spatial fabric byintroducing features that allow extractable fabric elements (EFEs) (forexample, PEs, network controllers, and/or switches) with variable anddynamically variable amounts of state to be extracted.

Embodiments of a CSA include a distributed data extraction protocol andmicroarchitecture to support this protocol. Certain embodiments of a CSAinclude multiple local extraction controllers (LECs) which streamprogram data out of their local region of the spatial fabric using acombination of a (e.g., small) set of control signals and thefabric-provided network. State elements may be used at each extractablefabric element (EFE) to form extraction chains, e.g., allowingindividual EFEs to self-extract without global addressing.

Embodiments of a CSA do not use a local network to extract program data.Embodiments of a CSA include specific hardware support (e.g., anextraction controller) for the formation of extraction chains, forexample, and do not rely on software to establish these chainsdynamically, e.g., at the cost of increasing extraction time.Embodiments of a CSA are not purely packet switched and do include extraout-of-band control wires (e.g., control is not sent through the datapath requiring extra cycles to strobe and reserialize this information).Embodiments of a CSA decrease extraction latency by fixing theextraction ordering and by providing explicit out-of-band control (e.g.,by at least a factor of two), while not significantly increasing networkcomplexity.

Embodiments of a CSA do not use a serial mechanism for data extraction,in which data is streamed bit by bit from the fabric using a JTAG-likeprotocol. Embodiments of a CSA utilize a coarse-grained fabric approach.In certain embodiments, adding a few control wires or state elements toa 64 or 32-bit-oriented CSA fabric has a lower cost relative to addingthose same control mechanisms to a 4 or 6 bit fabric.

FIG. 58 illustrates an accelerator tile 5800 comprising an array ofprocessing elements and a local extraction controller (5802, 5806)according to embodiments of the disclosure. Each PE, each networkcontroller, and each switch may be an extractable fabric elements(EFEs), e.g., which are configured (e.g., programmed) by embodiments ofthe CSA architecture.

Embodiments of a CSA include hardware that provides for efficient,distributed, low-latency extraction from a heterogeneous spatial fabric.This may be achieved according to four techniques. First, a hardwareentity, the local extraction controller (LEC) is utilized, for example,as in FIGS. 58-60. A LEC may accept commands from a host (for example, aprocessor core), e.g., extracting a stream of data from the spatialarray, and writing this data back to virtual memory for inspection bythe host. Second, a extraction data path may be included, e.g., that isas wide as the native width of the PE fabric and which may be overlaidon top of the PE fabric. Third, new control signals may be received intothe PE fabric which orchestrate the extraction process. Fourth, stateelements may be located (e.g., in a register) at each configurableendpoint which track the status of adjacent EFEs, allowing each EFE tounambiguously export its state without extra control signals. These fourmicroarchitectural features may allow a CSA to extract data from chainsof EFEs. To obtain low data extraction latency, certain embodiments maypartition the extraction problem by including multiple (e.g., many) LECsand EFE chains in the fabric. At extraction time, these chains mayoperate independently to extract data from the fabric in parallel, e.g.,dramatically reducing latency. As a result of these combinations, a CSAmay perform a complete state dump (e.g., in hundreds of nanoseconds).

FIGS. 59A-59C illustrate a local extraction controller 5902 configuringa data path network according to embodiments of the disclosure. Depictednetwork includes a plurality of multiplexers (e.g., multiplexers 5906,5908, 5910) that may be configured (e.g., via their respective controlsignals) to connect one or more data paths (e.g., from PEs) together.FIG. 59A illustrates the network 5900 (e.g., fabric) configured (e.g.,set) for some previous operation or program. FIG. 59B illustrates thelocal extraction controller 5902 (e.g., including a network interfacecircuit 5904 to send and/or receive signals) strobing an extractionsignal and all PEs controlled by the LEC enter into extraction mode. Thelast PE in the extraction chain (or an extraction terminator) may masterthe extraction channels (e.g., bus) and being sending data according toeither (1) signals from the LEC or (2) internally produced signals(e.g., from a PE). Once completed, a PE may set its completion flag,e.g., enabling the next PE to extract its data. FIG. 59C illustrates themost distant PE has completed the extraction process and as a result ithas set its extraction state bit or bits, e.g., which swing the muxesinto the adjacent network to enable the next PE to begin the extractionprocess. The extracted PE may resume normal operation. In someembodiments, the PE may remain disabled until other action is taken. Inthese figures, the multiplexor networks are analogues of the “Switch”shown in certain Figures (e.g., FIG. 6).

The following sections describe the operation of the various componentsof embodiments of an extraction network.

Local Extraction Controller

FIG. 60 illustrates an extraction controller 6002 according toembodiments of the disclosure. A local extraction controller (LEC) maybe the hardware entity which is responsible for accepting extractioncommands, coordinating the extraction process with the EFEs, and/orstoring extracted data, e.g., to virtual memory. In this capacity, theLEC may be a special-purpose, sequential microcontroller.

LEC operation may begin when it receives a pointer to a buffer (e.g., invirtual memory) where fabric state will be written, and, optionally, acommand controlling how much of the fabric will be extracted. Dependingon the LEC microarchitecture, this pointer (e.g., stored in pointerregister 6004) may come either over a network or through a memory systemaccess to the LEC. When it receives such a pointer (e.g., command), theLEC proceeds to extract state from the portion of the fabric for whichit is responsible. The LEC may stream this extracted data out of thefabric into the buffer provided by the external caller.

Two different microarchitectures for the LEC are shown in FIG. 58. Thefirst places the LEC 5802 at the memory interface. In this case, the LECmay make direct requests to the memory system to write extracted data.In the second case the LEC 5806 is placed on a memory network, in whichit may make requests to the memory only indirectly. In both cases, thelogical operation of the LEC may be unchanged. In one embodiment, LECsare informed of the desire to extract data from the fabric, for example,by a set of (e.g., OS-visible) control-status-registers which will beused to inform individual LECs of new commands.

Extra Out-Of-band Control Channels (e.g., Wires)

In certain embodiments, extraction relies on 2-8 extra, out-of-bandsignals to improve configuration speed, as defined below. Signals drivenby the LEC may be labelled LEC. Signals driven by the EFE (e.g., PE) maybe labelled EFE. Configuration controller 6002 may include the followingcontrol channels, e.g., LEC_EXTRACT control channel 6106, LEC_STARTcontrol channel 6008, LEC_STROBE control channel 6010, and EFE_COMPLETEcontrol channel 6012, with examples of each discussed in Table 3 below.

TABLE 3 Extraction Channels LEC_EXTRACT Optional signal asserted by theLEC during extraction process. Lowering this signal causes normaloperation to resume. LEC_START Signal denoting start of extraction,allowing setup of local EFE state LEC_STROBE Optional strobe signal forcontrolling extraction related state machines at EFEs. EFEs may generatethis signal internally in some implementations. EFE_COMPLETE Optionalsignal strobed when EFE has completed dumping state. This helps LECidentify the completion of individual EFE dumps.

Generally, the handling of extraction may be left to the implementer ofa particular EFE. For example, selectable function EFE may have aprovision for dumping registers using an existing data path, while afixed function EFE might simply have a multiplexor.

Due to long wire delays when programming a large set of EFEs, theLEC_STROBE signal may be treated as a clock/latch enable for EFEcomponents. Since this signal is used as a clock, in one embodiment theduty cycle of the line is at most 50%. As a result, extractionthroughput is approximately halved. Optionally, a second LEC_STROBEsignal may be added to enable continuous extraction.

In one embodiment, only LEC_START is strictly communicated on anindependent coupling (e.g., wire), for example, other control channelsmay be overlayed on existing network (e.g., wires).

Reuse of Network Resources

To reduce the overhead of data extraction, certain embodiments of a CSAmake use of existing network infrastructure to communicate extractiondata. A LEC may make use of both a chip-level memory hierarchy and afabric-level communications networks to move data from the fabric intostorage. As a result, in certain embodiments of a CSA, the extractioninfrastructure adds no more than 2% to the overall fabric area andpower.

Reuse of network resources in certain embodiments of a CSA may cause anetwork to have some hardware support for an extraction protocol.Circuit switched networks require of certain embodiments of a CSA causea LEC to set their multiplexors in a specific way for configuration whenthe ‘LEC_START’ signal is asserted. Packet switched networks may notrequire extension, although LEC endpoints (e.g., extraction terminators)use a specific address in the packet switched network. Network reuse isoptional, and some embodiments may find dedicated configuration buses tobe more convenient.

Per EFE State

Each EFE may maintain a bit denoting whether or not it has exported itsstate. This bit may de-asserted when the extraction start signal isdriven, and then asserted once the particular EFE finished extraction.In one extraction protocol, EFEs are arranged to form chains with theEFE extraction state bit determining the topology of the chain. A EFEmay read the extraction state bit of the immediately adjacent EFE. Ifthis adjacent EFE has its extraction bit set and the current EFE doesnot, the EFE may determine that it owns the extraction bus. When an EFEdumps its last data value, it may drives the ‘EFE_DONE’ signal and setsits extraction bit, e.g., enabling upstream EFEs to configure forextraction. The network adjacent to the EFE may observe this signal andalso adjust its state to handle the transition. As a base case to theextraction process, an extraction terminator (e.g., extractionterminator 5804 for LEC 5802 or extraction terminator 5808 for LEC 5806in FIG. 49) which asserts that extraction is complete may be included atthe end of a chain.

Internal to the EFE, this bit may be used to drive flow control readysignals. For example, when the extraction bit is de-asserted, networkcontrol signals may automatically be clamped to a values that preventdata from flowing, while, within PEs, no operations or actions will bescheduled.

Dealing with High-Delay Paths

One embodiment of a LEC may drive a signal over a long distance, e.g.,through many multiplexors and with many loads. Thus, it may be difficultfor a signal to arrive at a distant EFE within a short clock cycle. Incertain embodiments, extraction signals are at some division (e.g.,fraction of) of the main (e.g., CSA) clock frequency to ensure digitaltiming discipline at extraction. Clock division may be utilized in anout-of-band signaling protocol, and does not require any modification ofthe main clock tree.

Ensuring Consistent Fabric Behavior During Extraction

Since certain extraction scheme are distributed and havenon-deterministic timing due to program and memory effects, differentmembers of the fabric may be under extraction at different times. WhileLEC_EXTRACT is driven, all network flow control signals may be drivenlogically low, e.g., thus freezing the operation of a particular segmentof the fabric.

An extraction process may be non-destructive. Therefore a set of PEs maybe considered operational once extraction has completed. An extension toan extraction protocol may allow PEs to optionally be disabled postextraction. Alternatively, beginning configuration during the extractionprocess will have similar effect in embodiments.

Single PE Extraction

In some cases, it may be expedient to extract a single PE. In this case,an optional address signal may be driven as part of the commencement ofthe extraction process. This may enable the PE targeted for extractionto be directly enabled. Once this PE has been extracted, the extractionprocess may cease with the lowering of the LEC_EXTRACT signal. In thisway, a single PE may be selectively extracted, e.g., by the localextraction controller.

Handling Extraction Backpressure

In an embodiment where the LEC writes extracted data to memory (forexample, for post-processing, e.g., in software), it may be subject tolimitted memory bandwidth. In the case that the LEC exhausts itsbuffering capacity, or expects that it will exhaust its bufferingcapacity, it may stops strobing the LEC_STROBE signal until thebuffering issue has resolved.

Note that in certain figures (e.g., FIGS. 49, 52, 53, 55, 56, and 58)communications are shown schematically. In certain embodiments, thosecommunications may occur over the (e.g., interconnect) network.

6.7 Flow Diagrams

FIG. 61 illustrates a flow diagram 6100 according to embodiments of thedisclosure. Depicted flow 6100 includes decoding an instruction with adecoder of a core of a processor into a decoded instruction 6102;executing the decoded instruction with an execution unit of the core ofthe processor to perform a first operation 6104; receiving an input of adataflow graph comprising a plurality of nodes 6106; overlaying thedataflow graph into an array of processing elements of the processorwith each node represented as a dataflow operator in the array ofprocessing elements 6108; and performing a second operation of thedataflow graph with the array of processing elements when an incomingoperand set arrives at the array of processing elements 6110.

FIG. 62 illustrates a flow diagram 6200 according to embodiments of thedisclosure. Depicted flow 6200 includes decoding an instruction with adecoder of a core of a processor into a decoded instruction 6202;executing the decoded instruction with an execution unit of the core ofthe processor to perform a first operation 6204; receiving an input of adataflow graph comprising a plurality of nodes 6206; overlaying thedataflow graph into a plurality of processing elements of the processorand an interconnect network between the plurality of processing elementsof the processor with each node represented as a dataflow operator inthe plurality of processing elements 6208; and performing a secondoperation of the dataflow graph with the interconnect network and theplurality of processing elements when an incoming operand set arrives atthe plurality of processing elements 6210.

6.8 Memory

FIG. 63A is a block diagram of a system 6300 that employs a memoryordering circuit 6305 interposed between a memory subsystem 6310 andacceleration hardware 6302, according to an embodiment of the presentdisclosure. The memory subsystem 6310 may include known memorycomponents, including cache, memory, and one or more memorycontroller(s) associated with a processor-based architecture. Theacceleration hardware 6302 may be coarse-grained spatial architecturemade up of lightweight processing elements (or other types of processingcomponents) connected by an inter-processing element (PE) network oranother type of inter-component network.

In one embodiment, programs, viewed as control data flow graphs, aremapped onto the spatial architecture by configuring PEs and acommunications network. Generally, PEs are configured as dataflowoperators, similar to functional units in a processor: once the inputoperands arrive at the PE, some operation occurs, and results areforwarded to downstream PEs in a pipelined fashion. Dataflow operators(or other types of operators) may choose to consume incoming data on aper-operator basis. Simple operators, like those handling theunconditional evaluation of arithmetic expressions often consume allincoming data. It is sometimes useful, however, for operators tomaintain state, for example, in accumulation.

The PEs communicate using dedicated virtual circuits, which are formedby statically configuring a circuit-switched communications network.These virtual circuits are flow controlled and fully back pressured,such that PEs will stall if either the source has no data or thedestination is full. At runtime, data flows through the PEs implementinga mapped algorithm according to a dataflow graph, also referred to as asubprogram herein. For example, data may be streamed in from memory,through the acceleration hardware 6302, and then back out to memory.Such an architecture can achieve remarkable performance efficiencyrelative to traditional multicore processors: compute, in the form ofPEs, is simpler and more numerous than larger cores and communication isdirect, as opposed to an extension of the memory subsystem 6310. Memorysystem parallelism, however, helps to support parallel PE computation.If memory accesses are serialized, high parallelism is likelyunachievable. To facilitate parallelism of memory accesses, thedisclosed memory ordering circuit 6305 includes memory orderingarchitecture and microarchitecture, as will be explained in detail. Inone embodiment, the memory ordering circuit 6305 is a request addressfile circuit (or “RAF”) or other memory request circuitry.

FIG. 63B is a block diagram of the system 6300 of FIG. 63A but whichemploys multiple memory ordering circuits 6305, according to anembodiment of the present disclosure. Each memory ordering circuit 6305may function as an interface between the memory subsystem 6310 and aportion of the acceleration hardware 6302 (e.g., spatial array ofprocessing elements or tile). The memory subsystem 6310 may include aplurality of cache slices 12 (e.g., cache slices 12A, 12B, 12C, and 12Din the embodiment of FIG. 63B), and a certain number of memory orderingcircuits 6305 (four in this embodiment) may be used for each cache slice12. A crossbar 6304 (e.g., RAF circuit) may connect the memory orderingcircuits 6305 to banks of cache that make up each cache slice 12A, 12B,12C, and 12D. For example, there may be eight banks of memory in eachcache slice in one embodiment. The system 6300 may be instantiated on asingle die, for example, as a system on a chip (SoC). In one embodiment,the SoC includes the acceleration hardware 6302. In an alternativeembodiment, the acceleration hardware 6302 is an external programmablechip such as an FPGA or CGRA, and the memory ordering circuits 6305interface with the acceleration hardware 6302 through an input/outputhub or the like.

Each memory ordering circuit 6305 may accept read and write requests tothe memory subsystem 6310. The requests from the acceleration hardware6302 arrive at the memory ordering circuit 6305 in a separate channelfor each node of the dataflow graph that initiates read or writeaccesses, also referred to as load or store accesses herein. Bufferingis provided so that the processing of loads will return the requesteddata to the acceleration hardware 6302 in the order it was requested. Inother words, iteration six data is returned before iteration seven data,and so forth. Furthermore, note that the request channel from a memoryordering circuit 6305 to a particular cache bank may be implemented asan ordered channel and any first request that leaves before a secondrequest will arrive at the cache bank before the second request.

FIG. 64 is a block diagram 6400 illustrating general functioning ofmemory operations into and out of the acceleration hardware 6302,according to an embodiment of the present disclosure. The operationsoccurring out the top of the acceleration hardware 6302 are understoodto be made to and from a memory of the memory subsystem 6310. Note thattwo load requests are made, followed by corresponding load responses.While the acceleration hardware 6302 performs processing on data fromthe load responses, a third load request and response occur, whichtrigger additional acceleration hardware processing. The results of theacceleration hardware processing for these three load operations arethen passed into a store operation, and thus a final result is storedback to memory.

By considering this sequence of operations, it may be evident thatspatial arrays more naturally map to channels. Furthermore, theacceleration hardware 6302 is latency-insensitive in terms of therequest and response channels, and inherent parallel processing that mayoccur. The acceleration hardware may also decouple execution of aprogram from implementation of the memory subsystem 6310 (FIG. 63A), asinterfacing with the memory occurs at discrete moments separate frommultiple processing steps taken by the acceleration hardware 6302. Forexample, a load request to and a load response from memory are separateactions, and may be scheduled differently in different circumstancesdepending on dependency flow of memory operations. The use of spatialfabric, for example, for processing instructions facilitates spatialseparation and distribution of such a load request and a load response.

FIG. 65 is a block diagram 6500 illustrating a spatial dependency flowfor a store operation 6501, according to an embodiment of the presentdisclosure. Reference to a store operation is exemplary, as the sameflow may apply to a load operation (but without incoming data), or toother operators such as a fence. A fence is an ordering operation formemory subsystems that ensures that all prior memory operations of atype (such as all stores or all loads) have completed. The storeoperation 6501 may receive an address 6502 (of memory) and data 6504received from the acceleration hardware 6302. The store operation 6501may also receive an incoming dependency token 6508, and in response tothe availability of these three items, the store operation 6501 maygenerate an outgoing dependency token 6512. The incoming dependencytoken, which may, for example, be an initial dependency token of aprogram, may be provided in a compiler-supplied configuration for theprogram, or may be provided by execution of memory-mapped input/output(I/O). Alternatively, if the program has already been running, theincoming dependency token 6508 may be received from the accelerationhardware 6302, e.g., in association with a preceding memory operationfrom which the store operation 6501 depends. The outgoing dependencytoken 6512 may be generated based on the address 6502 and data 6504being required by a program-subsequent memory operation.

FIG. 66 is a detailed block diagram of the memory ordering circuit 6305of FIG. 63A, according to an embodiment of the present disclosure. Thememory ordering circuit 6305 may be coupled to an out-of-order memorysubsystem 6310, which as discussed, may include cache 12 and memory 18,and associated out-of-order memory controller(s). The memory orderingcircuit 6305 may include, or be coupled to, a communications networkinterface 20 that may be either an inter-tile or an intra-tile networkinterface, and may be a circuit switched network interface (asillustrated), and thus include circuit-switched interconnects.Alternatively, or additionally, the communications network interface 20may include packet-switched interconnects.

The memory ordering circuit 6305 may further include, but not be limitedto, a memory interface 6610, an operations queue 6612, input queue(s)6616, a completion queue 6620, an operation configuration data structure6624, and an operations manager circuit 6630 that may further include ascheduler circuit 6632 and an execution circuit 6634. In one embodiment,the memory interface 6610 may be circuit-switched, and in anotherembodiment, the memory interface 6610 may be packet-switched, or bothmay exist simultaneously. The operations queue 6612 may buffer memoryoperations (with corresponding arguments) that are being processed forrequest, and may, therefore, correspond to addresses and data cominginto the input queues 6616.

More specifically, the input queues 6616 may be an aggregation of atleast the following: a load address queue, a store address queue, astore data queue, and a dependency queue. When implementing the inputqueue 6616 as aggregated, the memory ordering circuit 6305 may providefor sharing of logical queues, with additional control logic tologically separate the queues, which are individual channels with thememory ordering circuit. This may maximize input queue usage, but mayalso require additional complexity and space for the logic circuitry tomanage the logical separation of the aggregated queue. Alternatively, aswill be discussed with reference to FIG. 67, the input queues 6616 maybe implemented in a segregated fashion, with a separate hardware queuefor each. Whether aggregated (FIG. 66) or disaggregated (FIG. 67),implementation for purposes of this disclosure is substantially thesame, with the former using additional logic to logically separate thequeues within a single, shared hardware queue.

When shared, the input queues 6616 and the completion queue 6620 may beimplemented as ring buffers of a fixed size. A ring buffer is anefficient implementation of a circular queue that has afirst-in-first-out (FIFO) data characteristic. These queues may,therefore, enforce a semantical order of a program for which the memoryoperations are being requested. In one embodiment, a ring buffer (suchas for the store address queue) may have entries corresponding toentries flowing through an associated queue (such as the store dataqueue or the dependency queue) at the same rate. In this way, a storeaddress may remain associated with corresponding store data.

More specifically, the load address queue may buffer an incoming addressof the memory 18 from which to retrieve data. The store address queuemay buffer an incoming address of the memory 18 to which to write data,which is buffered in the store data queue. The dependency queue maybuffer dependency tokens in association with the addresses of the loadaddress queue and the store address queue. Each queue, representing aseparate channel, may be implemented with a fixed or dynamic number ofentries. When fixed, the more entries that are available, the moreefficient complicated loop processing may be made. But, having too manyentries costs more area and energy to implement. In some cases, e.g.,with the aggregated architecture, the disclosed input queue 6616 mayshare queue slots. Use of the slots in a queue may be staticallyallocated.

The completion queue 6620 may be a separate set of queues to buffer datareceived from memory in response to memory commands issued by loadoperations. The completion queue 6620 may be used to hold a loadoperation that has been scheduled but for which data has not yet beenreceived (and thus has not yet completed). The completion queue 6620,may therefore, be used to reorder data and operation flow.

The operations manager circuit 6630, which will be explained in moredetail with reference to FIGS. 67 through 22, may provide logic forscheduling and executing queued memory operations when taking intoaccount dependency tokens used to provide correct ordering of the memoryoperations. The operation manager 6630 may access the operationconfiguration data structure 6624 to determine which queues are groupedtogether to form a given memory operation. For example, the operationconfiguration data structure 6624 may include that a specific dependencycounter (or queue), input queue, output queue, and completion queue areall grouped together for a particular memory operation. As eachsuccessive memory operation may be assigned a different group of queues,access to varying queues may be interleaved across a sub-program ofmemory operations. Knowing all of these queues, the operations managercircuit 6630 may interface with the operations queue 6612, the inputqueue(s) 6616, the completion queue(s) 6620, and the memory subsystem6310 to initially issue memory operations to the memory subsystem 6310when successive memory operations become “executable,” and to nextcomplete the memory operation with some acknowledgement from the memorysubsystem. This acknowledgement may be, for example, data in response toa load operation command or an acknowledgement of data being stored inthe memory in response to a store operation command.

FIG. 67 is a flow diagram of a microarchitecture 6700 of the memoryordering circuit 6305 of FIG. 63A, according to an embodiment of thepresent disclosure. The memory subsystem 6310 may allow illegalexecution of a program in which ordering of memory operations is wrong,due to the semantics of C language (and other object-oriented programlanguages). The microarchitecture 6700 may enforce the ordering of thememory operations (sequences of loads from and stores to memory) so thatresults of instructions that the acceleration hardware 6302 executes areproperly ordered. A number of local networks 50 are illustrated torepresent a portion of the acceleration hardware 6302 coupled to themicroarchitecture 6700.

From an architectural perspective, there are at least two goals: first,to run general sequential codes correctly, and second, to obtain highperformance in the memory operations performed by the microarchitecture6700. To ensure program correctness, the compiler expresses thedependency between the store operation and the load operation to anarray, p, in some fashion, which are expressed via dependency tokens aswill be explained. To improve performance, the microarchitecture 6700finds and issues as many load commands of an array in parallel as islegal with respect to program order.

In one embodiment, the microarchitecture 6700 may include the operationsqueue 6612, the input queues 6616, the completion queues 6620, and theoperations manager circuit 6630 discussed with reference to FIG. 66,above, where individual queues may be referred to as channels. Themicroarchitecture 6700 may further include a plurality of dependencytoken counters 6714 (e.g., one per input queue), a set of dependencyqueues 6718 (e.g., one each per input queue), an address multiplexer6732, a store data multiplexer 6734, a completion queue indexmultiplexer 6736, and a load data multiplexer 6738. The operationsmanager circuit 6630, in one embodiment, may direct these variousmultiplexers in generating a memory command 6750 (to be sent to thememory subsystem 6310) and in receipt of responses of load commands backfrom the memory subsystem 6310, as will be explained.

The input queues 6616, as mentioned, may include a load address queue6722, a store address queue 6724, and a store data queue 6726. (Thesmall numbers 0, 1, 2 are channel labels and will be referred to laterin FIG. 70 and FIG. 73A.) In various embodiments, these input queues maybe multiplied to contain additional channels, to handle additionalparallelization of memory operation processing. Each dependency queue6718 may be associated with one of the input queues 6616. Morespecifically, the dependency queue 6718 labeled B0 may be associatedwith the load address queue 6722 and the dependency queue labeled B1 maybe associated with the store address queue 6724. If additional channelsof the input queues 6616 are provided, the dependency queues 6718 mayinclude additional, corresponding channels.

In one embodiment, the completion queues 6620 may include a set ofoutput buffers 6744 and 6746 for receipt of load data from the memorysubsystem 6310 and a completion queue 6742 to buffer addresses and datafor load operations according to an index maintained by the operationsmanager circuit 6630. The operations manager circuit 6630 can manage theindex to ensure in-order execution of the load operations, and toidentify data received into the output buffers 6744 and 6746 that may bemoved to scheduled load operations in the completion queue 6742.

More specifically, because the memory subsystem 6310 is out of order,but the acceleration hardware 6302 completes operations in order, themicroarchitecture 6700 may re-order memory operations with use of thecompletion queue 6742. Three different sub-operations may be performedin relation to the completion queue 6742, namely to allocate, enqueue,and dequeue. For allocation, the operations manager circuit 6630 mayallocate an index into the completion queue 6742 in an in-order nextslot of the completion queue. The operations manager circuit may providethis index to the memory subsystem 6310, which may then know the slot towhich to write data for a load operation. To enqueue, the memorysubsystem 6310 may write data as an entry to the indexed, in-order nextslot in the completion queue 6742 like random access memory (RAM),setting a status bit of the entry to valid. To dequeue, the operationsmanager circuit 6630 may present the data stored in this in-order nextslot to complete the load operation, setting the status bit of the entryto invalid. Invalid entries may then be available for a new allocation.

In one embodiment, the status signals 6648 may refer to statuses of theinput queues 6616, the completion queues 6620, the dependency queues6718, and the dependency token counters 6714. These statuses, forexample, may include an input status, an output status, and a controlstatus, which may refer to the presence or absence of a dependency tokenin association with an input or an output. The input status may includethe presence or absence of addresses and the output status may includethe presence or absence of store values and available completion bufferslots. The dependency token counters 6714 may be a compactrepresentation of a queue and track a number of dependency tokens usedfor any given input queue. If the dependency token counters 6714saturate, no additional dependency tokens may be generated for newmemory operations. Accordingly, the memory ordering circuit 6305 maystall scheduling new memory operations until the dependency tokencounters 6714 becomes unsaturated.

With additional reference to FIG. 68, FIG. 68 is a block diagram of anexecutable determiner circuit 6800, according to an embodiment of thepresent disclosure. The memory ordering circuit 6305 may be set up withseveral different kinds of memory operations, for example a load and astore:

ldNo[d,x] result.outN, addr.in64, order.in0, order.out0

stNo[d,x] addr.in64, data.inN, order.in0, order.out0

The executable determiner circuit 6800 may be integrated as a part ofthe scheduler circuit 6632 and which may perform a logical operation todetermine whether a given memory operation is executable, and thus readyto be issued to memory. A memory operation may be executed when thequeues corresponding to its memory arguments have data and an associateddependency token is present. These memory arguments may include, forexample, an input queue identifier 6810 (indicative of a channel of theinput queue 6616), an output queue identifier 6820 (indicative of achannel of the completion queues 6620), a dependency queue identifier6830 (e.g., what dependency queue or counter should be referenced), andan operation type indicator 6840 (e.g., load operation or storeoperation). A field (e.g., of a memory request) may be included, e.g.,in the above format, that stores a bit or bits to indicate to use thehazard checking hardware.

These memory arguments may be queued within the operations queue 6612,and used to schedule issuance of memory operations in association withincoming addresses and data from memory and the acceleration hardware6302. (See FIG. 80.) Incoming status signals 6648 may be logicallycombined with these identifiers and then the results may be added (e.g.,through an AND gate 6850) to output an executable signal, e.g., which isasserted when the memory operation is executable. The incoming statussignals 6648 may include an input status 6812 for the input queueidentifier 6810, an output status 6822 for the output queue identifier6820, and a control status 6832 (related to dependency tokens) for thedependency queue identifier 6830.

For a load operation, and by way of example, the memory ordering circuit6305 may issue a load command when the load operation has an address(input status) and room to buffer the load result in the completionqueue 6742 (output status). Similarly, the memory ordering circuit 6305may issue a store command for a store operation when the store operationhas both an address and data value (input status). Accordingly, thestatus signals 6648 may communicate a level of emptiness (or fullness)of the queues to which the status signals pertain. The operation typemay then dictate whether the logic results in an executable signaldepending on what address and data should be available.

To implement dependency ordering, the scheduler circuit 6632 may extendmemory operations to include dependency tokens as underlined above inthe example load and store operations. The control status 6832 mayindicate whether a dependency token is available within the dependencyqueue identified by the dependency queue identifier 6830, which could beone of the dependency queues 6718 (for an incoming memory operation) ora dependency token counter 6714 (for a completed memory operation).Under this formulation, a dependent memory operation requires anadditional ordering token to execute and generates an additionalordering token upon completion of the memory operation, where completionmeans that data from the result of the memory operation has becomeavailable to program-subsequent memory operations.

In one embodiment, with further reference to FIG. 67, the operationsmanager circuit 6630 may direct the address multiplexer 6732 to selectan address argument that is buffered within either the load addressqueue 6722 or the store address queue 6724, depending on whether a loadoperation or a store operation is currently being scheduled forexecution. If it is a store operation, the operations manager circuit6630 may also direct the store data multiplexer 6734 to selectcorresponding data from the store data queue 6726. The operationsmanager circuit 6630 may also direct the completion queue indexmultiplexer 6736 to retrieve a load operation entry, indexed accordingto queue status and/or program order, within the completion queues 6620,to complete a load operation. The operations manager circuit 6630 mayalso direct the load data multiplexer 6738 to select data received fromthe memory subsystem 6310 into the completion queues 6620 for a loadoperation that is awaiting completion. In this way, the operationsmanager circuit 6630 may direct selection of inputs that go into formingthe memory command 6750, e.g., a load command or a store command, orthat the execution circuit 6634 is waiting for to complete a memoryoperation.

FIG. 69 is a block diagram the execution circuit 6634 that may include apriority encoder 6906 and selection circuitry 6908 and which generatesoutput control line(s) 6910, according to one embodiment of the presentdisclosure. In one embodiment, the execution circuit 6634 may accessqueued memory operations (in the operations queue 6612) that have beendetermined to be executable (FIG. 68). The execution circuit 6634 mayalso receive the schedules 6904A, 6904B, 6904C for multiple of thequeued memory operations that have been queued and also indicated asready to issue to memory. The priority encoder 6906 may thus receive anidentity of the executable memory operations that have been scheduledand execute certain rules (or follow particular logic) to select thememory operation from those coming in that has priority to be executedfirst. The priority encoder 6906 may output a selector signal 6907 thatidentifies the scheduled memory operation that has a highest priority,and has thus been selected.

The priority encoder 6906, for example, may be a circuit (such as astate machine or a simpler converter) that compresses multiple binaryinputs into a smaller number of outputs, including possibly just oneoutput. The output of a priority encoder is the binary representation ofthe original number starting from zero of the most significant inputbit. So, in one example, when memory operation 0 (“zero”), memoryoperation one (“1”), and memory operation two (“2”) are executable andscheduled, corresponding to 6904A, 6904B, and 6904C, respectively. Thepriority encoder 6906 may be configured to output the selector signal6907 to the selection circuitry 6908 indicating the memory operationzero as the memory operation that has highest priority. The selectioncircuitry 6908 may be a multiplexer in one embodiment, and be configuredto output its selection (e.g., of memory operation zero) onto thecontrol lines 6910, as a control signal, in response to the selectorsignal from the priority encoder 6906 (and indicative of selection ofmemory operation of highest priority). This control signal may go to themultiplexers 6732, 6734, 6736, and/or 6738, as discussed with referenceto FIG. 67, to populate the memory command 6750 that is next to issue(be sent) to the memory subsystem 6310. The transmittal of the memorycommand may be understood to be issuance of a memory operation to thememory subsystem 6310.

FIG. 70 is a block diagram of an exemplary load operation 7000, bothlogical and in binary form, according to an embodiment of the presentdisclosure. Referring back to FIG. 68, the logical representation of theload operation 7000 may include channel zero (“0”) (corresponding to theload address queue 6722) as the input queue identifier 6810 andcompletion channel one (“1”) (corresponding to the output buffer 6744)as the output queue identifier 6820. The dependency queue identifier6830 may include two identifiers, channel B0 (corresponding to the firstof the dependency queues 6718) for incoming dependency tokens andcounter C0 for outgoing dependency tokens. The operation type 6840 hasan indication of “Load,” which could be a numerical indicator as well,to indicate the memory operation is a load operation. Below the logicalrepresentation of the logical memory operation is a binaryrepresentation for exemplary purposes, e.g., where a load is indicatedby “00.” The load operation of FIG. 70 may be extended to include otherconfigurations such as a store operation (FIG. 72A) or other type ofmemory operations, such as a fence.

An example of memory ordering by the memory ordering circuit 6305 willbe illustrated with a simplified example for purposes of explanationwith relation to FIGS. 71A-71B, 72A-72B, and 73A-73G. For this example,the following code includes an array, p, which is accessed by indices iand i+2:

  for(i) {  temp = p[i];   p[i+2] = temp; }

Assume, for this example, that array p contains 0,1,2,3,4,5,6, and atthe end of loop execution, array p will contain 0,1,0,1,0,1,0. This codemay be transformed by unrolling the loop, as illustrated in FIGS. 71Aand 71B. True address dependencies are annotated by arrows in FIG. 71A,which in each case, a load operation is dependent on a store operationto the same address. For example, for the first of such dependencies, astore (e.g., a write) to p[2] needs to occur before a load (e.g., aread) from p[2], and second of such dependencies, a store to p[3] needsto occur before a load from p[3], and so forth. As a compiler is to bepessimistic, the compiler annotates dependencies between two memoryoperations, load p[i] and store p[i+2]. Note that only sometimes doreads and writes conflict. The micro-architecture 6700 is designed toextract memory-level parallelism where memory operations may moveforward at the same time when there are no conflicts to the sameaddress. This is especially the case for load operations, which exposelatency in code execution due to waiting for preceding dependent storeoperations to complete. In the example code in FIG. 71B, safereorderings are noted by the arrows on the left of the unfolded code.

The way the microarchitecture may perform this reordering is discussedwith reference to FIGS. 72A-72B and 73A-73G. Note that this approach isnot as optimal as possible because the microarchitecture 6700 may notsend a memory command to memory every cycle. However, with minimalhardware, the microarchitecture supports dependency flows by executingmemory operations when operands (e.g., address and data, for a store, oraddress for a load) and dependency tokens are available.

FIG. 72A is a block diagram of exemplary memory arguments for a loadoperation 7202 and for a store operation 7204, according to anembodiment of the present disclosure. These, or similar, memoryarguments were discussed with relation to FIG. 70 and will not berepeated here. Note, however, that the store operation 7204 has noindicator for the output queue identifier because no data is beingoutput to the acceleration hardware 6302. Instead, the store address inchannel 1 and the data in channel 2 of the input queues 6616, asidentified in the input queue identifier memory argument, are to bescheduled for transmission to the memory subsystem 6310 in a memorycommand to complete the store operation 7204. Furthermore, the inputchannels and output channels of the dependency queues are bothimplemented with counters. Because the load operations and the storeoperations as displayed in FIGS. 71A and 71B are interdependent, thecounters may be cycled between the load operations and the storeoperations within the flow of the code.

FIG. 72B is a block diagram illustrating flow of the load operations andstore operations, such as the load operation 7202 and the store 7204operation of FIG. 71A, through the microarchitecture 6700 of the memoryordering circuit of FIG. 67, according to an embodiment of the presentdisclosure. For simplicity of explanation, not all of the components aredisplayed, but reference may be made back to the additional componentsdisplayed in FIG. 67. Various ovals indicating “Load” for the loadoperation 7202 and “Store” for the store operation 7204 are overlaid onsome of the components of the microarchitecture 6700 as indication ofhow various channels of the queues are being used as the memoryoperations are queued and ordered through the microarchitecture 6700.

FIGS. 73A, 73B, 73C, 73D, 73E, 73F, 73G, and 73H are block diagramsillustrating functional flow of load operations and store operations forthe exemplary program of FIGS. 71A and 71B through queues of themicroarchitecture of FIG. 72B, according to an embodiment of the presentdisclosure. Each figure may correspond to a next cycle of processing bythe microarchitecture 6700. Values that are italicized are incomingvalues (into the queues) and values that are bolded are outgoing values(out of the queues). All other values with normal fonts are retainedvalues already existing in the queues.

In FIG. 73A, the address p[0] is incoming into the load address queue6722, and the address p[2] is incoming into the store address queue6724, starting the control flow process. Note that counter C0, fordependency input for the load address queue, is “1” and counter C1, fordependency output, is zero. In contrast, the “1” of C0 indicates adependency out value for the store operation. This indicates an incomingdependency for the load operation of p[0] and an outgoing dependency forthe store operation of p[2]. These values, however, are not yet active,but will become active, in this way, in FIG. 73B.

In FIG. 73B, address p[0] is bolded to indicate it is outgoing in thiscycle. A new address p[1] is incoming into the load address queue and anew address p[3] is incoming into the store address queue. A zero(“0”)-valued bit in the completion queue 6742 is also incoming, whichindicates any data present for that indexed entry is invalid. Asmentioned, the values for the counters C0 and C1 are now indicated asincoming, and are thus now active this cycle.

In FIG. 73C, the outgoing address p[0] has now left the load addressqueue and a new address p[2] is incoming into the load address queue.And, the data (“0”) is incoming into the completion queue for addressp[0]. The validity bit is set to “1” to indicate that the data in thecompletion queue is valid. Furthermore, a new address p[4] is incominginto the store address queue. The value for counter C0 is indicated asoutgoing and the value for counter C1 is indicated as incoming. Thevalue of “1” for C1 indicates an incoming dependency for store operationto address p[4].

Note that the address p[2] for the newest load operation is dependent onthe value that first needs to be stored by the store operation foraddress p[2], which is at the top of the store address queue. Later, theindexed entry in the completion queue for the load operation fromaddress p[2] may remain buffered until the data from the store operationto the address p[2] is completed (see FIGS. 73F-73H).

In FIG. 73D, the data (“0”) is outgoing from the completion queue foraddress p[0], which is therefore being sent out to the accelerationhardware 6302. Furthermore, a new address p[3] is incoming into the loadaddress queue and a new address p[5] is incoming into the store addressqueue. The values for the counters C0 and C1 remain unchanged.

In FIG. 73E, the value (“0”) for the address p[2] is incoming into thestore data queue, while a new address p[4] comes into the load addressqueue and a new address p[6] comes into the store address queue. Thecounter values for C0 and C1 remain unchanged.

In FIG. 73F, the value (“0”) for the address p[2] in the store dataqueue, and the address p[2] in the store address queue are both outgoingvalues. Likewise, the value for the counter C1 is indicated as outgoing,while the value (“0”) for counter C0 remain unchanged. Furthermore, anew address p[5] is incoming into the load address queue and a newaddress p[7] is incoming into the store address queue.

In FIG. 73G, the value (“0”) is incoming to indicate the indexed valuewithin the completion queue 6742 is invalid. The address p[1] is boldedto indicate it is outgoing from the load address queue while a newaddress p[6] is incoming into the load address queue. A new address p[8]is also incoming into the store address queue. The value of counter C0is incoming as a “1,” corresponding to an incoming dependency for theload operation of address p[6] and an outgoing dependency for the storeoperation of address p[8]. The value of counter C1 is now “0,” and isindicated as outgoing.

In FIG. 73H, a data value of “1” is incoming into the completion queue6742 while the validity bit is also incoming as a “1,” meaning that thebuffered data is valid. This is the data needed to complete the loadoperation for p[2]. Recall that this data had to first be stored toaddress p[2], which happened in FIG. 73F. The value of “0” for counterC0 is outgoing, and a value of “1,” for counter C1 is incoming.Furthermore, a new address p[7] is incoming into the load address queueand a new address p[9] is incoming into the store address queue.

In the present embodiment, the process of executing the code of FIGS.71A and 71B may continue on with bouncing dependency tokens between “0”and “1” for the load operations and the store operations. This is due tothe tight dependencies between p[i] and p[i+2]. Other code with lessfrequent dependencies may generate dependency tokens at a slower rate,and thus reset the counters C0 and C1 at a slower rate, causing thegeneration of tokens of higher values (corresponding to furthersemantically-separated memory operations).

FIG. 74 is a flow chart of a method 7400 for ordering memory operationsbetween acceleration hardware and an out-of-order memory subsystem,according to an embodiment of the present disclosure. The method 7400may be performed by a system that may include hardware (e.g., circuitry,dedicated logic, and/or programmable logic), software (e.g.,instructions executable on a computer system to perform hardwaresimulation), or a combination thereof. In an illustrative example, themethod 7400 may be performed by the memory ordering circuit 6305 andvarious subcomponents of the memory ordering circuit 6305.

More specifically, referring to FIG. 74, the method 7400 may start withthe memory ordering circuit queuing memory operations in an operationsqueue of the memory ordering circuit (7410). Memory operation andcontrol arguments may make up the memory operations, as queued, wherethe memory operation and control arguments are mapped to certain queueswithin the memory ordering circuit as discussed previously. The memoryordering circuit may work to issue the memory operations to a memory inassociation with acceleration hardware, to ensure the memory operationscomplete in program order. The method 7400 may continue with the memoryordering circuit receiving, in set of input queues, from theacceleration hardware, an address of the memory associated with a secondmemory operation of the memory operations (7420). In one embodiment, aload address queue of the set of input queues is the channel to receivethe address. In another embodiment, a store address queue of the set ofinput queues is the channel to receive the address. The method 7400 maycontinue with the memory ordering circuit receiving, from theacceleration hardware, a dependency token associated with the address,wherein the dependency token indicates a dependency on data generated bya first memory operation, of the memory operations, which precedes thesecond memory operation (7430). In one embodiment, a channel of adependency queue is to receive the dependency token. The first memoryoperation may be either a load operation or a store operation.

The method 7400 may continue with the memory ordering circuit schedulingissuance of the second memory operation to the memory in response toreceiving the dependency token and the address associated with thedependency token (7440). For example, when the load address queuereceives the address for an address argument of a load operation and thedependency queue receives the dependency token for a control argument ofthe load operation, the memory ordering circuit may schedule issuance ofthe second memory operation as a load operation. The method 7400 maycontinue with the memory ordering circuit issuing the second memoryoperation (e.g., in a command) to the memory in response to completionof the first memory operation (7450). For example, if the first memoryoperation is a store, completion may be verified by acknowledgement thatthe data in a store data queue of the set of input queues has beenwritten to the address in the memory. Similarly, if the first memoryoperation is a load operation, completion may be verified by receipt ofdata from the memory for the load operation.

7. Summary

Supercomputing at the ExaFLOP scale may be a challenge inhigh-performance computing, a challenge which is not likely to be met byconventional von Neumann architectures. To achieve ExaFLOPs, embodimentsof a CSA provide a heterogeneous spatial array that targets directexecution of (e.g., compiler-produced) dataflow graphs. In addition tolaying out the architectural principles of embodiments of a CSA, theabove also describes and evaluates embodiments of a CSA which showedperformance and energy of larger than 10× over existing products.Compiler-generated code may have significant performance and energygains over roadmap architectures. As a heterogeneous, parametricarchitecture, embodiments of a CSA may be readily adapted to allcomputing uses. For example, a mobile version of CSA might be tuned to32-bits, while a machine-learning focused array might featuresignificant numbers of vectorized 8-bit multiplication units. The mainadvantages of embodiments of a CSA are high performance and extremeenergy efficiency, characteristics relevant to all forms of computingranging from supercomputing and datacenter to the internet-of-things.

In one embodiment, a processor includes a spatial array of processingelements; and a packet switched communications network to route datawithin the spatial array between processing elements according to adataflow graph to perform a first dataflow operation of the dataflowgraph, wherein the packet switched communications network furthercomprises a plurality of network dataflow endpoint circuits to perform asecond dataflow operation of the dataflow graph. A network dataflowendpoint circuit of the plurality of network dataflow endpoint circuitsmay include a network ingress buffer to receive input data from thepacket switched communications network; and a spatial array egressbuffer to output resultant data to the spatial array of processingelements according to the second dataflow operation on the input data.The spatial array egress buffer may output the resultant data based on ascheduler within the network dataflow endpoint circuit monitoring thepacket switched communications network. The spatial array egress buffermay output the resultant data based on the scheduler within the networkdataflow endpoint circuit monitoring a selected channel of multiplenetwork virtual channels of the packet switched communications network.A network dataflow endpoint circuit of the plurality of network dataflowendpoint circuits may include a spatial array ingress buffer to receivecontrol data from the spatial array that causes a network ingress bufferof the network dataflow endpoint circuit that received input data fromthe packet switched communications network to output resultant data tothe spatial array of processing elements according to the seconddataflow operation on the input data and the control data. A networkdataflow endpoint circuit of the plurality of network dataflow endpointcircuits may stall an output of resultant data of the second dataflowoperation from a spatial array egress buffer of the network dataflowendpoint circuit when a backpressure signal from a downstream processingelement of the spatial array of processing elements indicates thatstorage in the downstream processing element is not available for theoutput of the network dataflow endpoint circuit. A network dataflowendpoint circuit of the plurality of network dataflow endpoint circuitsmay send a backpressure signal to stall a source from sending input dataon the packet switched communications network into a network ingressbuffer of the network dataflow endpoint circuit when the network ingressbuffer is not available. The spatial array of processing elements mayinclude a plurality of processing elements; and an interconnect networkbetween the plurality of processing elements to receive an input of thedataflow graph comprising a plurality of nodes, wherein the dataflowgraph is to be overlaid into the interconnect network, the plurality ofprocessing elements, and the plurality of network dataflow endpointcircuits with each node represented as a dataflow operator in either ofthe plurality of processing elements and the plurality of networkdataflow endpoint circuits, and the plurality of processing elements andthe plurality of network dataflow endpoint circuits are to perform anoperation by an incoming operand set arriving at each of the dataflowoperators of the plurality of processing elements and the plurality ofnetwork dataflow endpoint circuits. The spatial array of processingelements may include a circuit switched network to transport the datawithin the spatial array between processing elements according to thedataflow graph.

In another embodiment, a method includes providing a spatial array ofprocessing elements; routing, with a packet switched communicationsnetwork, data within the spatial array between processing elementsaccording to a dataflow graph; performing a first dataflow operation ofthe dataflow graph with the processing elements; and performing a seconddataflow operation of the dataflow graph with a plurality of networkdataflow endpoint circuits of the packet switched communicationsnetwork. The performing the second dataflow operation may includereceiving input data from the packet switched communications networkwith a network ingress buffer of a network dataflow endpoint circuit ofthe plurality of network dataflow endpoint circuits; and outputtingresultant data from a spatial array egress buffer of the networkdataflow endpoint circuit to the spatial array of processing elementsaccording to the second dataflow operation on the input data. Theoutputting may include outputting the resultant data based on ascheduler within the network dataflow endpoint circuit monitoring thepacket switched communications network. The outputting may includeoutputting the resultant data based on the scheduler within the networkdataflow endpoint circuit monitoring a selected channel of multiplenetwork virtual channels of the packet switched communications network.The performing the second dataflow operation may include receivingcontrol data, with a spatial array ingress buffer of a network dataflowendpoint circuit of the plurality of network dataflow endpoint circuits,from the spatial array; and configuring the network dataflow endpointcircuit to cause a network ingress buffer of the network dataflowendpoint circuit that received input data from the packet switchedcommunications network to output resultant data to the spatial array ofprocessing elements according to the second dataflow operation on theinput data and the control data. The performing the second dataflowoperation may include stalling an output of the second dataflowoperation from a spatial array egress buffer of a network dataflowendpoint circuit of the plurality of network dataflow endpoint circuitswhen a backpressure signal from a downstream processing element of thespatial array of processing elements indicates that storage in thedownstream processing element is not available for the output of thenetwork dataflow endpoint circuit. The performing the second dataflowoperation may include sending a backpressure signal from a networkdataflow endpoint circuit of the plurality of network dataflow endpointcircuits to stall a source from sending input data on the packetswitched communications network into a network ingress buffer of thenetwork dataflow endpoint circuit when the network ingress buffer is notavailable. The routing, performing the first dataflow operation, andperforming the second dataflow operation may include receiving an inputof a dataflow graph comprising a plurality of nodes; overlaying thedataflow graph into the spatial array of processing elements and theplurality of network dataflow endpoint circuits with each noderepresented as a dataflow operator in either of the processing elementsand the plurality of network dataflow endpoint circuits; and performingthe first dataflow operation with the processing elements and performingthe second dataflow operation with the plurality of network dataflowendpoint circuits when an incoming operand set arrives at each of thedataflow operators of the processing elements and the plurality ofnetwork dataflow endpoint circuits. The method may include transportingthe data within the spatial array between processing elements accordingto the dataflow graph with a circuit switched network of the spatialarray.

In yet another embodiment, a non-transitory machine readable medium thatstores code that when executed by a machine causes the machine toperform a method including providing a spatial array of processingelements; routing, with a packet switched communications network, datawithin the spatial array between processing elements according to adataflow graph; performing a first dataflow operation of the dataflowgraph with the processing elements; and performing a second dataflowoperation of the dataflow graph with a plurality of network dataflowendpoint circuits of the packet switched communications network. Theperforming the second dataflow operation may include receiving inputdata from the packet switched communications network with a networkingress buffer of a network dataflow endpoint circuit of the pluralityof network dataflow endpoint circuits; and outputting resultant datafrom a spatial array egress buffer of the network dataflow endpointcircuit to the spatial array of processing elements according to thesecond dataflow operation on the input data. The outputting may includeoutputting the resultant data based on a scheduler within the networkdataflow endpoint circuit monitoring the packet switched communicationsnetwork. The outputting may include outputting the resultant data basedon the scheduler within the network dataflow endpoint circuit monitoringa selected channel of multiple network virtual channels of the packetswitched communications network. The performing the second dataflowoperation may include receiving control data, with a spatial arrayingress buffer of a network dataflow endpoint circuit of the pluralityof network dataflow endpoint circuits, from the spatial array; andconfiguring the network dataflow endpoint circuit to cause a networkingress buffer of the network dataflow endpoint circuit that receivedinput data from the packet switched communications network to outputresultant data to the spatial array of processing elements according tothe second dataflow operation on the input data and the control data.The performing the second dataflow operation may include stalling anoutput of the second dataflow operation from a spatial array egressbuffer of a network dataflow endpoint circuit of the plurality ofnetwork dataflow endpoint circuits when a backpressure signal from adownstream processing element of the spatial array of processingelements indicates that storage in the downstream processing element isnot available for the output of the network dataflow endpoint circuit.The performing the second dataflow operation may include sending abackpressure signal from a network dataflow endpoint circuit of theplurality of network dataflow endpoint circuits to stall a source fromsending input data on the packet switched communications network into anetwork ingress buffer of the network dataflow endpoint circuit when thenetwork ingress buffer is not available. The routing, performing thefirst dataflow operation, and performing the second dataflow operationmay include receiving an input of a dataflow graph comprising aplurality of nodes; overlaying the dataflow graph into the spatial arrayof processing elements and the plurality of network dataflow endpointcircuits with each node represented as a dataflow operator in either ofthe processing elements and the plurality of network dataflow endpointcircuits; and performing the first dataflow operation with theprocessing elements and performing the second dataflow operation withthe plurality of network dataflow endpoint circuits when an incomingoperand set arrives at each of the dataflow operators of the processingelements and the plurality of network dataflow endpoint circuits. Themethod may include transporting the data within the spatial arraybetween processing elements according to the dataflow graph with acircuit switched network of the spatial array.

In another embodiment, a processor includes a spatial array ofprocessing elements; and a packet switched communications network toroute data within the spatial array between processing elementsaccording to a dataflow graph to perform a first dataflow operation ofthe dataflow graph, wherein the packet switched communications networkfurther comprises means to perform a second dataflow operation of thedataflow graph.

In one embodiment, a processor includes a core with a decoder to decodean instruction into a decoded instruction and an execution unit toexecute the decoded instruction to perform a first operation; aplurality of processing elements; and an interconnect network betweenthe plurality of processing elements to receive an input of a dataflowgraph comprising a plurality of nodes, wherein the dataflow graph is tobe overlaid into the interconnect network and the plurality ofprocessing elements with each node represented as a dataflow operator inthe plurality of processing elements, and the plurality of processingelements are to perform a second operation by a respective, incomingoperand set arriving at each of the dataflow operators of the pluralityof processing elements. A processing element of the plurality ofprocessing elements may stall execution when a backpressure signal froma downstream processing element indicates that storage in the downstreamprocessing element is not available for an output of the processingelement. The processor may include a flow control path network to carrythe backpressure signal according to the dataflow graph. A dataflowtoken may cause an output from a dataflow operator receiving thedataflow token to be sent to an input buffer of a particular processingelement of the plurality of processing elements. The second operationmay include a memory access and the plurality of processing elementscomprises a memory-accessing dataflow operator that is not to performthe memory access until receiving a memory dependency token from alogically previous dataflow operator. The plurality of processingelements may include a first type of processing element and a second,different type of processing element.

In another embodiment, a method includes decoding an instruction with adecoder of a core of a processor into a decoded instruction; executingthe decoded instruction with an execution unit of the core of theprocessor to perform a first operation; receiving an input of a dataflowgraph comprising a plurality of nodes; overlaying the dataflow graphinto a plurality of processing elements of the processor and aninterconnect network between the plurality of processing elements of theprocessor with each node represented as a dataflow operator in theplurality of processing elements; and performing a second operation ofthe dataflow graph with the interconnect network and the plurality ofprocessing elements by a respective, incoming operand set arriving ateach of the dataflow operators of the plurality of processing elements.The method may include stalling execution by a processing element of theplurality of processing elements when a backpressure signal from adownstream processing element indicates that storage in the downstreamprocessing element is not available for an output of the processingelement. The method may include sending the backpressure signal on aflow control path network according to the dataflow graph. A dataflowtoken may cause an output from a dataflow operator receiving thedataflow token to be sent to an input buffer of a particular processingelement of the plurality of processing elements. The method may includenot performing a memory access until receiving a memory dependency tokenfrom a logically previous dataflow operator, wherein the secondoperation comprises the memory access and the plurality of processingelements comprises a memory-accessing dataflow operator. The method mayinclude providing a first type of processing element and a second,different type of processing element of the plurality of processingelements.

In yet another embodiment, an apparatus includes a data path networkbetween a plurality of processing elements; and a flow control pathnetwork between the plurality of processing elements, wherein the datapath network and the flow control path network are to receive an inputof a dataflow graph comprising a plurality of nodes, the dataflow graphis to be overlaid into the data path network, the flow control pathnetwork, and the plurality of processing elements with each noderepresented as a dataflow operator in the plurality of processingelements, and the plurality of processing elements are to perform asecond operation by a respective, incoming operand set arriving at eachof the dataflow operators of the plurality of processing elements. Theflow control path network may carry backpressure signals to a pluralityof dataflow operators according to the dataflow graph. A dataflow tokensent on the data path network to a dataflow operator may cause an outputfrom the dataflow operator to be sent to an input buffer of a particularprocessing element of the plurality of processing elements on the datapath network. The data path network may be a static, circuit switchednetwork to carry the respective, input operand set to each of thedataflow operators according to the dataflow graph. The flow controlpath network may transmit a backpressure signal according to thedataflow graph from a downstream processing element to indicate thatstorage in the downstream processing element is not available for anoutput of the processing element. At least one data path of the datapath network and at least one flow control path of the flow control pathnetwork may form a channelized circuit with backpressure control. Theflow control path network may pipeline at least two of the plurality ofprocessing elements in series.

In another embodiment, a method includes receiving an input of adataflow graph comprising a plurality of nodes; and overlaying thedataflow graph into a plurality of processing elements of a processor, adata path network between the plurality of processing elements, and aflow control path network between the plurality of processing elementswith each node represented as a dataflow operator in the plurality ofprocessing elements. The method may include carrying backpressuresignals with the flow control path network to a plurality of dataflowoperators according to the dataflow graph. The method may includesending a dataflow token on the data path network to a dataflow operatorto cause an output from the dataflow operator to be sent to an inputbuffer of a particular processing element of the plurality of processingelements on the data path network. The method may include setting aplurality of switches of the data path network and/or a plurality ofswitches of the flow control path network to carry the respective, inputoperand set to each of the dataflow operators according to the dataflowgraph, wherein the data path network is a static, circuit switchednetwork. The method may include transmitting a backpressure signal withthe flow control path network according to the dataflow graph from adownstream processing element to indicate that storage in the downstreamprocessing element is not available for an output of the processingelement. The method may include forming a channelized circuit withbackpressure control with at least one data path of the data pathnetwork and at least one flow control path of the flow control pathnetwork.

In yet another embodiment, a processor includes a core with a decoder todecode an instruction into a decoded instruction and an execution unitto execute the decoded instruction to perform a first operation; aplurality of processing elements; and a network means between theplurality of processing elements to receive an input of a dataflow graphcomprising a plurality of nodes, wherein the dataflow graph is to beoverlaid into the network means and the plurality of processing elementswith each node represented as a dataflow operator in the plurality ofprocessing elements, and the plurality of processing elements are toperform a second operation by a respective, incoming operand setarriving at each of the dataflow operators of the plurality ofprocessing elements.

In another embodiment, an apparatus includes a data path means between aplurality of processing elements; and a flow control path means betweenthe plurality of processing elements, wherein the data path means andthe flow control path means are to receive an input of a dataflow graphcomprising a plurality of nodes, the dataflow graph is to be overlaidinto the data path means, the flow control path means, and the pluralityof processing elements with each node represented as a dataflow operatorin the plurality of processing elements, and the plurality of processingelements are to perform a second operation by a respective, incomingoperand set arriving at each of the dataflow operators of the pluralityof processing elements.

In one embodiment, a processor includes a core with a decoder to decodean instruction into a decoded instruction and an execution unit toexecute the decoded instruction to perform a first operation; and anarray of processing elements to receive an input of a dataflow graphcomprising a plurality of nodes, wherein the dataflow graph is to beoverlaid into the array of processing elements with each noderepresented as a dataflow operator in the array of processing elements,and the array of processing elements is to perform a second operationwhen an incoming operand set arrives at the array of processingelements. The array of processing element may not perform the secondoperation until the incoming operand set arrives at the array ofprocessing elements and storage in the array of processing elements isavailable for output of the second operation. The array of processingelements may include a network (or channel(s)) to carry dataflow tokensand control tokens to a plurality of dataflow operators. The secondoperation may include a memory access and the array of processingelements may include a memory-accessing dataflow operator that is not toperform the memory access until receiving a memory dependency token froma logically previous dataflow operator. Each processing element mayperform only one or two operations of the dataflow graph.

In another embodiment, a method includes decoding an instruction with adecoder of a core of a processor into a decoded instruction; executingthe decoded instruction with an execution unit of the core of theprocessor to perform a first operation; receiving an input of a dataflowgraph comprising a plurality of nodes; overlaying the dataflow graphinto an array of processing elements of the processor with each noderepresented as a dataflow operator in the array of processing elements;and performing a second operation of the dataflow graph with the arrayof processing elements when an incoming operand set arrives at the arrayof processing elements. The array of processing elements may not performthe second operation until the incoming operand set arrives at the arrayof processing elements and storage in the array of processing elementsis available for output of the second operation. The array of processingelements may include a network carrying dataflow tokens and controltokens to a plurality of dataflow operators. The second operation mayinclude a memory access and the array of processing elements comprises amemory-accessing dataflow operator that is not to perform the memoryaccess until receiving a memory dependency token from a logicallyprevious dataflow operator. Each processing element may performs onlyone or two operations of the dataflow graph.

In yet another embodiment, a non-transitory machine readable medium thatstores code that when executed by a machine causes the machine toperform a method including decoding an instruction with a decoder of acore of a processor into a decoded instruction; executing the decodedinstruction with an execution unit of the core of the processor toperform a first operation; receiving an input of a dataflow graphcomprising a plurality of nodes; overlaying the dataflow graph into anarray of processing elements of the processor with each node representedas a dataflow operator in the array of processing elements; andperforming a second operation of the dataflow graph with the array ofprocessing elements when an incoming operand set arrives at the array ofprocessing elements. The array of processing element may not perform thesecond operation until the incoming operand set arrives at the array ofprocessing elements and storage in the array of processing elements isavailable for output of the second operation. The array of processingelements may include a network carrying dataflow tokens and controltokens to a plurality of dataflow operators. The second operation mayinclude a memory access and the array of processing elements comprises amemory-accessing dataflow operator that is not to perform the memoryaccess until receiving a memory dependency token from a logicallyprevious dataflow operator. Each processing element may performs onlyone or two operations of the dataflow graph.

In another embodiment, a processor includes a core with a decoder todecode an instruction into a decoded instruction and an execution unitto execute the decoded instruction to perform a first operation; andmeans to receive an input of a dataflow graph comprising a plurality ofnodes, wherein the dataflow graph is to be overlaid into the means witheach node represented as a dataflow operator in the means, and the meansis to perform a second operation when an incoming operand set arrives atthe means.

In one embodiment, a processor includes a core with a decoder to decodean instruction into a decoded instruction and an execution unit toexecute the decoded instruction to perform a first operation; aplurality of processing elements; and an interconnect network betweenthe plurality of processing elements to receive an input of a dataflowgraph comprising a plurality of nodes, wherein the dataflow graph is tobe overlaid into the interconnect network and the plurality ofprocessing elements with each node represented as a dataflow operator inthe plurality of processing elements, and the plurality of processingelements is to perform a second operation when an incoming operand setarrives at the plurality of processing elements. The processor mayfurther comprise a plurality of configuration controllers, eachconfiguration controller is coupled to a respective subset of theplurality of processing elements, and each configuration controller isto load configuration information from storage and cause coupling of therespective subset of the plurality of processing elements according tothe configuration information. The processor may include a plurality ofconfiguration caches, and each configuration controller is coupled to arespective configuration cache to fetch the configuration informationfor the respective subset of the plurality of processing elements. Thefirst operation performed by the execution unit may prefetchconfiguration information into each of the plurality of configurationcaches. Each of the plurality of configuration controllers may include areconfiguration circuit to cause a reconfiguration for at least oneprocessing element of the respective subset of the plurality ofprocessing elements on receipt of a configuration error message from theat least one processing element. Each of the plurality of configurationcontrollers may a reconfiguration circuit to cause a reconfiguration forthe respective subset of the plurality of processing elements on receiptof a reconfiguration request message, and disable communication with therespective subset of the plurality of processing elements until thereconfiguration is complete. The processor may include a plurality ofexception aggregators, and each exception aggregator is coupled to arespective subset of the plurality of processing elements to collectexceptions from the respective subset of the plurality of processingelements and forward the exceptions to the core for servicing. Theprocessor may include a plurality of extraction controllers, eachextraction controller is coupled to a respective subset of the pluralityof processing elements, and each extraction controller is to cause statedata from the respective subset of the plurality of processing elementsto be saved to memory.

In another embodiment, a method includes decoding an instruction with adecoder of a core of a processor into a decoded instruction; executingthe decoded instruction with an execution unit of the core of theprocessor to perform a first operation; receiving an input of a dataflowgraph comprising a plurality of nodes; overlaying the dataflow graphinto a plurality of processing elements of the processor and aninterconnect network between the plurality of processing elements of theprocessor with each node represented as a dataflow operator in theplurality of processing elements; and performing a second operation ofthe dataflow graph with the interconnect network and the plurality ofprocessing elements when an incoming operand set arrives at theplurality of processing elements. The method may include loadingconfiguration information from storage for respective subsets of theplurality of processing elements and causing coupling for eachrespective subset of the plurality of processing elements according tothe configuration information. The method may include fetching theconfiguration information for the respective subset of the plurality ofprocessing elements from a respective configuration cache of a pluralityof configuration caches. The first operation performed by the executionunit may be prefetching configuration information into each of theplurality of configuration caches. The method may include causing areconfiguration for at least one processing element of the respectivesubset of the plurality of processing elements on receipt of aconfiguration error message from the at least one processing element.The method may include causing a reconfiguration for the respectivesubset of the plurality of processing elements on receipt of areconfiguration request message; and disabling communication with therespective subset of the plurality of processing elements until thereconfiguration is complete. The method may include collectingexceptions from a respective subset of the plurality of processingelements; and forwarding the exceptions to the core for servicing. Themethod may include causing state data from a respective subset of theplurality of processing elements to be saved to memory.

In yet another embodiment, a non-transitory machine readable medium thatstores code that when executed by a machine causes the machine toperform a method including decoding an instruction with a decoder of acore of a processor into a decoded instruction; executing the decodedinstruction with an execution unit of the core of the processor toperform a first operation; receiving an input of a dataflow graphcomprising a plurality of nodes; overlaying the dataflow graph into aplurality of processing elements of the processor and an interconnectnetwork between the plurality of processing elements of the processorwith each node represented as a dataflow operator in the plurality ofprocessing elements; and performing a second operation of the dataflowgraph with the interconnect network and the plurality of processingelements when an incoming operand set arrives at the plurality ofprocessing elements. The method may include loading configurationinformation from storage for respective subsets of the plurality ofprocessing elements and causing coupling for each respective subset ofthe plurality of processing elements according to the configurationinformation. The method may include fetching the configurationinformation for the respective subset of the plurality of processingelements from a respective configuration cache of a plurality ofconfiguration caches. The first operation performed by the executionunit may be prefetching configuration information into each of theplurality of configuration caches. The method may include causing areconfiguration for at least one processing element of the respectivesubset of the plurality of processing elements on receipt of aconfiguration error message from the at least one processing element.The method may include causing a reconfiguration for the respectivesubset of the plurality of processing elements on receipt of areconfiguration request message; and disabling communication with therespective subset of the plurality of processing elements until thereconfiguration is complete. The method may include collectingexceptions from a respective subset of the plurality of processingelements; and forwarding the exceptions to the core for servicing. Themethod may include causing state data from a respective subset of theplurality of processing elements to be saved to memory.

In another embodiment, a processor includes a core with a decoder todecode an instruction into a decoded instruction and an execution unitto execute the decoded instruction to perform a first operation; aplurality of processing elements; and means between the plurality ofprocessing elements to receive an input of a dataflow graph comprising aplurality of nodes, wherein the dataflow graph is to be overlaid intothe m and the plurality of processing elements with each noderepresented as a dataflow operator in the plurality of processingelements, and the plurality of processing elements is to perform asecond operation when an incoming operand set arrives at the pluralityof processing elements.

In one embodiment, an apparatus (e.g., a processor) includes: a spatialarray of processing elements to receive an input of a dataflow graphcomprising a plurality of nodes, wherein the dataflow graph is to beoverlaid into the spatial array of processing elements with each noderepresented as a dataflow operator in the spatial array of processingelements, and the spatial array of processing elements is to perform anoperation by a respective, incoming operand set arriving at each of thedataflow operators; a plurality of request address file circuits coupledto the spatial array of processing elements and a cache memory, eachrequest address file circuit of the plurality of request address filecircuits to access data in the cache memory in response to a request fordata access from the spatial array of processing elements; a pluralityof translation lookaside buffers comprising a translation lookasidebuffer in each of the plurality of request address file circuits toprovide an output of a physical address for an input of a virtualaddress; and a translation lookaside buffer manager circuit comprising ahigher-level translation lookaside buffer than the plurality oftranslation lookaside buffers, the translation lookaside buffer managercircuit to perform a first page walk in the cache memory for a miss ofan input of a virtual address into a first translation lookaside bufferand into the higher-level translation lookaside buffer to determine aphysical address mapped to the virtual address, and store a mapping ofthe virtual address to the physical address from the first page walk inthe higher-level translation lookaside buffer to cause the higher-leveltranslation lookaside buffer to send the physical address to the firsttranslation lookaside buffer in a first request address file circuit.The translation lookaside buffer manager circuit may concurrently, withthe first page walk, perform a second page walk in the cache memory,wherein the second page walk is for a miss of an input of a virtualaddress into a second translation lookaside buffer and into thehigher-level translation lookaside buffer to determine a physicaladdress mapped to the virtual address, and store a mapping of thevirtual address to the physical address from the second page walk in thehigher-level translation lookaside buffer to cause the higher-leveltranslation lookaside buffer to send the physical address to the secondtranslation lookaside buffer in a second request address file circuit.The receipt of the physical address in the first translation lookasidebuffer may cause the first request address file circuit to perform adata access for the request for data access from the spatial array ofprocessing elements on the physical address in the cache memory. Thetranslation lookaside buffer manager circuit may insert an indicator inthe higher-level translation lookaside buffer for the miss of the inputof the virtual address in the first translation lookaside buffer and thehigher-level translation lookaside buffer to prevent an additional pagewalk for the input of the virtual address during the first page walk.The translation lookaside buffer manager circuit may receive a shootdownmessage from a requesting entity for a mapping of a physical address toa virtual address, invalidate the mapping in the higher-leveltranslation lookaside buffer, and send shootdown messages to only thoseof the plurality of request address file circuits that include a copy ofthe mapping in a respective translation lookaside buffer, wherein eachof those of the plurality of request address file circuits are to sendan acknowledgement message to the translation lookaside buffer managercircuit, and the translation lookaside buffer manager circuit is to senda shootdown completion acknowledgment message to the requesting entitywhen all acknowledgement messages are received. The translationlookaside buffer manager circuit may receive a shootdown message from arequesting entity for a mapping of a physical address to a virtualaddress, invalidate the mapping in the higher-level translationlookaside buffer, and send shootdown messages to all of the plurality ofrequest address file circuits, wherein each of the plurality of requestaddress file circuits are to send an acknowledgement message to thetranslation lookaside buffer manager circuit, and the translationlookaside buffer manager circuit is to send a shootdown completionacknowledgment message to the requesting entity when all acknowledgementmessages are received.

In another embodiment, a method includes overlaying an input of adataflow graph comprising a plurality of nodes into a spatial array ofprocessing elements with each node represented as a dataflow operator inthe spatial array of processing elements; coupling a plurality ofrequest address file circuits to the spatial array of processingelements and a cache memory with each request address file circuit ofthe plurality of request address file circuits accessing data in thecache memory in response to a request for data access from the spatialarray of processing elements; providing an output of a physical addressfor an input of a virtual address into a translation lookaside buffer ofa plurality of translation lookaside buffers comprising a translationlookaside buffer in each of the plurality of request address filecircuits; coupling a translation lookaside buffer manager circuitcomprising a higher-level translation lookaside buffer than theplurality of translation lookaside buffers to the plurality of requestaddress file circuits and the cache memory; and performing a first pagewalk in the cache memory for a miss of an input of a virtual addressinto a first translation lookaside buffer and into the higher-leveltranslation lookaside buffer with the translation lookaside buffermanager circuit to determine a physical address mapped to the virtualaddress, and store a mapping of the virtual address to the physicaladdress from the first page walk in the higher-level translationlookaside buffer to cause the higher-level translation lookaside bufferto send the physical address to the first translation lookaside bufferin a first request address file circuit. The method may includeconcurrently, with the first page walk, performing a second page walk inthe cache memory with the translation lookaside buffer manager circuit,wherein the second page walk is for a miss of an input of a virtualaddress into a second translation lookaside buffer and into thehigher-level translation lookaside buffer to determine a physicaladdress mapped to the virtual address, and storing a mapping of thevirtual address to the physical address from the second page walk in thehigher-level translation lookaside buffer to cause the higher-leveltranslation lookaside buffer to send the physical address to the secondtranslation lookaside buffer in a second request address file circuit.The method may include causing the first request address file circuit toperform a data access for the request for data access from the spatialarray of processing elements on the physical address in the cache memoryin response to receipt of the physical address in the first translationlookaside buffer. The method may include inserting, with the translationlookaside buffer manager circuit, an indicator in the higher-leveltranslation lookaside buffer for the miss of the input of the virtualaddress in the first translation lookaside buffer and the higher-leveltranslation lookaside buffer to prevent an additional page walk for theinput of the virtual address during the first page walk. The method mayinclude receiving, with the translation lookaside buffer managercircuit, a shootdown message from a requesting entity for a mapping of aphysical address to a virtual address, invalidating the mapping in thehigher-level translation lookaside buffer, and sending shootdownmessages to only those of the plurality of request address file circuitsthat include a copy of the mapping in a respective translation lookasidebuffer, wherein each of those of the plurality of request address filecircuits are to send an acknowledgement message to the translationlookaside buffer manager circuit, and the translation lookaside buffermanager circuit is to send a shootdown completion acknowledgment messageto the requesting entity when all acknowledgement messages are received.The method may include receiving, with the translation lookaside buffermanager circuit, a shootdown message from a requesting entity for amapping of a physical address to a virtual address, invalidate themapping in the higher-level translation lookaside buffer, and sendingshootdown messages to all of the plurality of request address filecircuits, wherein each of the plurality of request address file circuitsare to send an acknowledgement message to the translation lookasidebuffer manager circuit, and the translation lookaside buffer managercircuit is to send a shootdown completion acknowledgment message to therequesting entity when all acknowledgement messages are received.

In another embodiment, an apparatus includes a spatial array ofprocessing elements to receive an input of a dataflow graph comprising aplurality of nodes, wherein the dataflow graph is to be overlaid intothe spatial array of processing elements with each node represented as adataflow operator in the spatial array of processing elements, and thespatial array of processing elements is to perform an operation by arespective, incoming operand set arriving at each of the dataflowoperators; a plurality of request address file circuits coupled to thespatial array of processing elements and a plurality of cache memorybanks, each request address file circuit of the plurality of requestaddress file circuits to access data in (e.g., each of) the plurality ofcache memory banks in response to a request for data access from thespatial array of processing elements; a plurality of translationlookaside buffers comprising a translation lookaside buffer in each ofthe plurality of request address file circuits to provide an output of aphysical address for an input of a virtual address; a plurality ofhigher-level, than the plurality of translation lookaside buffers,translation lookaside buffers comprising a higher-level translationlookaside buffer in each of the plurality of cache memory banks toprovide an output of a physical address for an input of a virtualaddress; and a translation lookaside buffer manager circuit to perform afirst page walk in the plurality of cache memory banks for a miss of aninput of a virtual address into a first translation lookaside buffer andinto a first higher-level translation lookaside buffer to determine aphysical address mapped to the virtual address, and store a mapping ofthe virtual address to the physical address from the first page walk inthe first higher-level translation lookaside buffer to cause the firsthigher-level translation lookaside buffer to send the physical addressto the first translation lookaside buffer in a first request addressfile circuit. The translation lookaside buffer manager circuit mayconcurrently, with the first page walk, perform a second page walk inthe plurality of cache memory banks, wherein the second page walk is fora miss of an input of a virtual address into a second translationlookaside buffer and into a second higher-level translation lookasidebuffer to determine a physical address mapped to the virtual address,and store a mapping of the virtual address to the physical address fromthe second page walk in the second higher-level translation lookasidebuffer to cause the second higher-level translation lookaside buffer tosend the physical address to the second translation lookaside buffer ina second request address file circuit. The receipt of the physicaladdress in the first translation lookaside buffer may cause the firstrequest address file circuit to perform a data access for the requestfor data access from the spatial array of processing elements on thephysical address in the plurality of cache memory banks. The translationlookaside buffer manager circuit may insert an indicator in the firsthigher-level translation lookaside buffer for the miss of the input ofthe virtual address in the first translation lookaside buffer and thefirst higher-level translation lookaside buffer to prevent an additionalpage walk for the input of the virtual address during the first pagewalk. The translation lookaside buffer manager circuit may receive ashootdown message from a requesting entity for a mapping of a physicaladdress to a virtual address, invalidate the mapping in a higher-leveltranslation lookaside buffer storing the mapping, and send shootdownmessages to only those of the plurality of request address file circuitsthat include a copy of the mapping in a respective translation lookasidebuffer, wherein each of those of the plurality of request address filecircuits are to send an acknowledgement message to the translationlookaside buffer manager circuit, and the translation lookaside buffermanager circuit is to send a shootdown completion acknowledgment messageto the requesting entity when all acknowledgement messages are received.The translation lookaside buffer manager circuit may receive a shootdownmessage from a requesting entity for a mapping of a physical address toa virtual address, invalidate the mapping in a higher-level translationlookaside buffer storing the mapping, and send shootdown messages to allof the plurality of request address file circuits, wherein each of theplurality of request address file circuits are to send anacknowledgement message to the translation lookaside buffer managercircuit, and the translation lookaside buffer manager circuit is to senda shootdown completion acknowledgment message to the requesting entitywhen all acknowledgement messages are received.

In yet another embodiment, a method includes: overlaying an input of adataflow graph comprising a plurality of nodes into a spatial array ofprocessing elements with each node represented as a dataflow operator inthe spatial array of processing elements; coupling a plurality ofrequest address file circuits to the spatial array of processingelements and a plurality of cache memory banks with each request addressfile circuit of the plurality of request address file circuits accessingdata in the plurality of cache memory banks in response to a request fordata access from the spatial array of processing elements;

providing an output of a physical address for an input of a virtualaddress into a translation lookaside buffer of a plurality oftranslation lookaside buffers comprising a translation lookaside bufferin each of the plurality of request address file circuits; providing anoutput of a physical address for an input of a virtual address into ahigher-level, than the plurality of translation lookaside buffers,translation lookaside buffer of a plurality of higher-level translationlookaside buffers comprising a higher-level translation lookaside bufferin each of the plurality of cache memory banks; coupling a translationlookaside buffer manager circuit to the plurality of request addressfile circuits and the plurality of cache memory banks; and performing afirst page walk in the plurality of cache memory banks for a miss of aninput of a virtual address into a first translation lookaside buffer andinto a first higher-level translation lookaside buffer with thetranslation lookaside buffer manager circuit to determine a physicaladdress mapped to the virtual address, and store a mapping of thevirtual address to the physical address from the first page walk in thefirst higher-level translation lookaside buffer to cause the firsthigher-level translation lookaside buffer to send the physical addressto the first translation lookaside buffer in a first request addressfile circuit. The method may include concurrently, with the first pagewalk, performing a second page walk in the plurality of cache memorybanks with the translation lookaside buffer manager circuit, wherein thesecond page walk is for a miss of an input of a virtual address into asecond translation lookaside buffer and into a second higher-leveltranslation lookaside buffer to determine a physical address mapped tothe virtual address, and storing a mapping of the virtual address to thephysical address from the second page walk in the second higher-leveltranslation lookaside buffer to cause the second higher-leveltranslation lookaside buffer to send the physical address to the secondtranslation lookaside buffer in a second request address file circuit.The method may include causing the first request address file circuit toperform a data access for the request for data access from the spatialarray of processing elements on the physical address in the plurality ofcache memory banks in response to receipt of the physical address in thefirst translation lookaside buffer. The method may include inserting,with the translation lookaside buffer manager circuit, an indicator inthe first higher-level translation lookaside buffer for the miss of theinput of the virtual address in the first translation lookaside bufferand the first higher-level translation lookaside buffer to prevent anadditional page walk for the input of the virtual address during thefirst page walk. The method may include receiving, with the translationlookaside buffer manager circuit, a shootdown message from a requestingentity for a mapping of a physical address to a virtual address,invalidating the mapping in a higher-level translation lookaside bufferstoring the mapping, and sending shootdown messages to only those of theplurality of request address file circuits that include a copy of themapping in a respective translation lookaside buffer, wherein each ofthose of the plurality of request address file circuits are to send anacknowledgement message to the translation lookaside buffer managercircuit, and the translation lookaside buffer manager circuit is to senda shootdown completion acknowledgment message to the requesting entitywhen all acknowledgement messages are received. The method may includereceiving, with the translation lookaside buffer manager circuit, ashootdown message from a requesting entity for a mapping of a physicaladdress to a virtual address, invalidate the mapping in a higher-leveltranslation lookaside buffer storing the mapping, and sending shootdownmessages to all of the plurality of request address file circuits,wherein each of the plurality of request address file circuits are tosend an acknowledgement message to the translation lookaside buffermanager circuit, and the translation lookaside buffer manager circuit isto send a shootdown completion acknowledgment message to the requestingentity when all acknowledgement messages are received.

In another embodiment, a system includes a core with a decoder to decodean instruction into a decoded instruction and an execution unit toexecute the decoded instruction to perform a first operation; a spatialarray of processing elements to receive an input of a dataflow graphcomprising a plurality of nodes, wherein the dataflow graph is to beoverlaid into the spatial array of processing elements with each noderepresented as a dataflow operator in the spatial array of processingelements, and the spatial array of processing elements is to perform asecond operation by a respective, incoming operand set arriving at eachof the dataflow operators; a plurality of request address file circuitscoupled to the spatial array of processing elements and a cache memory,each request address file circuit of the plurality of request addressfile circuits to access data in the cache memory in response to arequest for data access from the spatial array of processing elements; aplurality of translation lookaside buffers comprising a translationlookaside buffer in each of the plurality of request address filecircuits to provide an output of a physical address for an input of avirtual address; and a translation lookaside buffer manager circuitcomprising a higher-level translation lookaside buffer than theplurality of translation lookaside buffers, the translation lookasidebuffer manager circuit to perform a first page walk in the cache memoryfor a miss of an input of a virtual address into a first translationlookaside buffer and into the higher-level translation lookaside bufferto determine a physical address mapped to the virtual address, and storea mapping of the virtual address to the physical address from the firstpage walk in the higher-level translation lookaside buffer to cause thehigher-level translation lookaside buffer to send the physical addressto the first translation lookaside buffer in a first request addressfile circuit. The translation lookaside buffer manager circuit mayconcurrently, with the first page walk, perform a second page walk inthe cache memory, wherein the second page walk is for a miss of an inputof a virtual address into a second translation lookaside buffer and intothe higher-level translation lookaside buffer to determine a physicaladdress mapped to the virtual address, and store a mapping of thevirtual address to the physical address from the second page walk in thehigher-level translation lookaside buffer to cause the higher-leveltranslation lookaside buffer to send the physical address to the secondtranslation lookaside buffer in a second request address file circuit.The receipt of the physical address in the first translation lookasidebuffer may cause the first request address file circuit to perform adata access for the request for data access from the spatial array ofprocessing elements on the physical address in the cache memory. Thetranslation lookaside buffer manager circuit may insert an indicator inthe higher-level translation lookaside buffer for the miss of the inputof the virtual address in the first translation lookaside buffer and thehigher-level translation lookaside buffer to prevent an additional pagewalk for the input of the virtual address during the first page walk.The translation lookaside buffer manager circuit may receive a shootdownmessage from a requesting entity for a mapping of a physical address toa virtual address, invalidate the mapping in the higher-leveltranslation lookaside buffer, and send shootdown messages to only thoseof the plurality of request address file circuits that include a copy ofthe mapping in a respective translation lookaside buffer, wherein eachof those of the plurality of request address file circuits are to sendan acknowledgement message to the translation lookaside buffer managercircuit, and the translation lookaside buffer manager circuit is to senda shootdown completion acknowledgment message to the requesting entitywhen all acknowledgement messages are received. The translationlookaside buffer manager circuit may receive a shootdown message from arequesting entity for a mapping of a physical address to a virtualaddress, invalidate the mapping in the higher-level translationlookaside buffer, and send shootdown messages to all of the plurality ofrequest address file circuits, wherein each of the plurality of requestaddress file circuits are to send an acknowledgement message to thetranslation lookaside buffer manager circuit, and the translationlookaside buffer manager circuit is to send a shootdown completionacknowledgment message to the requesting entity when all acknowledgementmessages are received.

In yet another embodiment, a system includes a core with a decoder todecode an instruction into a decoded instruction and an execution unitto execute the decoded instruction to perform a first operation; aspatial array of processing elements to receive an input of a dataflowgraph comprising a plurality of nodes, wherein the dataflow graph is tobe overlaid into the spatial array of processing elements with each noderepresented as a dataflow operator in the spatial array of processingelements, and the spatial array of processing elements is to perform asecond operation by a respective, incoming operand set arriving at eachof the dataflow operators; a plurality of request address file circuitscoupled to the spatial array of processing elements and a plurality ofcache memory banks, each request address file circuit of the pluralityof request address file circuits to access data in (e.g., each of) theplurality of cache memory banks in response to a request for data accessfrom the spatial array of processing elements; a plurality oftranslation lookaside buffers comprising a translation lookaside bufferin each of the plurality of request address file circuits to provide anoutput of a physical address for an input of a virtual address; aplurality of higher-level, than the plurality of translation lookasidebuffers, translation lookaside buffers comprising a higher-leveltranslation lookaside buffer in each of the plurality of cache memorybanks to provide an output of a physical address for an input of avirtual address; and a translation lookaside buffer manager circuit toperform a first page walk in the plurality of cache memory banks for amiss of an input of a virtual address into a first translation lookasidebuffer and into a first higher-level translation lookaside buffer todetermine a physical address mapped to the virtual address, and store amapping of the virtual address to the physical address from the firstpage walk in the first higher-level translation lookaside buffer tocause the first higher-level translation lookaside buffer to send thephysical address to the first translation lookaside buffer in a firstrequest address file circuit. The translation lookaside buffer managercircuit may concurrently, with the first page walk, perform a secondpage walk in the plurality of cache memory banks, wherein the secondpage walk is for a miss of an input of a virtual address into a secondtranslation lookaside buffer and into a second higher-level translationlookaside buffer to determine a physical address mapped to the virtualaddress, and store a mapping of the virtual address to the physicaladdress from the second page walk in the second higher-level translationlookaside buffer to cause the second higher-level translation lookasidebuffer to send the physical address to the second translation lookasidebuffer in a second request address file circuit. The receipt of thephysical address in the first translation lookaside buffer may cause thefirst request address file circuit to perform a data access for therequest for data access from the spatial array of processing elements onthe physical address in the plurality of cache memory banks. Thetranslation lookaside buffer manager circuit may insert an indicator inthe first higher-level translation lookaside buffer for the miss of theinput of the virtual address in the first translation lookaside bufferand the first higher-level translation lookaside buffer to prevent anadditional page walk for the input of the virtual address during thefirst page walk. The translation lookaside buffer manager circuit mayreceive a shootdown message from a requesting entity for a mapping of aphysical address to a virtual address, invalidate the mapping in ahigher-level translation lookaside buffer storing the mapping, and sendshootdown messages to only those of the plurality of request addressfile circuits that include a copy of the mapping in a respectivetranslation lookaside buffer, wherein each of those of the plurality ofrequest address file circuits are to send an acknowledgement message tothe translation lookaside buffer manager circuit, and the translationlookaside buffer manager circuit is to send a shootdown completionacknowledgment message to the requesting entity when all acknowledgementmessages are received. The translation lookaside buffer manager circuitmay receive a shootdown message from a requesting entity for a mappingof a physical address to a virtual address, invalidate the mapping in ahigher-level translation lookaside buffer storing the mapping, and sendshootdown messages to all of the plurality of request address filecircuits, wherein each of the plurality of request address file circuitsare to send an acknowledgement message to the translation lookasidebuffer manager circuit, and the translation lookaside buffer managercircuit is to send a shootdown completion acknowledgment message to therequesting entity when all acknowledgement messages are received.

In another embodiment, an apparatus (e.g., a processor) includes: aspatial array of processing elements to receive an input of a dataflowgraph comprising a plurality of nodes, wherein the dataflow graph is tobe overlaid into the spatial array of processing elements with each noderepresented as a dataflow operator in the spatial array of processingelements, and the spatial array of processing elements is to perform anoperation by a respective, incoming operand set arriving at each of thedataflow operators; a plurality of request address file circuits coupledto the spatial array of processing elements and a cache memory, eachrequest address file circuit of the plurality of request address filecircuits to access data in the cache memory in response to a request fordata access from the spatial array of processing elements; a pluralityof translation lookaside buffers comprising a translation lookasidebuffer in each of the plurality of request address file circuits toprovide an output of a physical address for an input of a virtualaddress; and a means comprising a higher-level translation lookasidebuffer than the plurality of translation lookaside buffers, the means toperform a first page walk in the cache memory for a miss of an input ofa virtual address into a first translation lookaside buffer and into thehigher-level translation lookaside buffer to determine a physicaladdress mapped to the virtual address, and store a mapping of thevirtual address to the physical address from the first page walk in thehigher-level translation lookaside buffer to cause the higher-leveltranslation lookaside buffer to send the physical address to the firsttranslation lookaside buffer in a first request address file circuit.

In yet another embodiment, an apparatus includes a spatial array ofprocessing elements to receive an input of a dataflow graph comprising aplurality of nodes, wherein the dataflow graph is to be overlaid intothe spatial array of processing elements with each node represented as adataflow operator in the spatial array of processing elements, and thespatial array of processing elements is to perform an operation by arespective, incoming operand set arriving at each of the dataflowoperators; a plurality of request address file circuits coupled to thespatial array of processing elements and a plurality of cache memorybanks, each request address file circuit of the plurality of requestaddress file circuits to access data in (e.g., each of) the plurality ofcache memory banks in response to a request for data access from thespatial array of processing elements; a plurality of translationlookaside buffers comprising a translation lookaside buffer in each ofthe plurality of request address file circuits to provide an output of aphysical address for an input of a virtual address; a plurality ofhigher-level, than the plurality of translation lookaside buffers,translation lookaside buffers comprising a higher-level translationlookaside buffer in each of the plurality of cache memory banks toprovide an output of a physical address for an input of a virtualaddress; and a means to perform a first page walk in the plurality ofcache memory banks for a miss of an input of a virtual address into afirst translation lookaside buffer and into a first higher-leveltranslation lookaside buffer to determine a physical address mapped tothe virtual address, and store a mapping of the virtual address to thephysical address from the first page walk in the first higher-leveltranslation lookaside buffer to cause the first higher-level translationlookaside buffer to send the physical address to the first translationlookaside buffer in a first request address file circuit.

In another embodiment, an apparatus comprises a data storage device thatstores code that when executed by a hardware processor causes thehardware processor to perform any method disclosed herein. An apparatusmay be as described in the detailed description. A method may be asdescribed in the detailed description.

In yet another embodiment, a non-transitory machine readable medium thatstores code that when executed by a machine causes the machine toperform a method comprising any method disclosed herein.

An instruction set (e.g., for execution by a core) may include one ormore instruction formats. A given instruction format may define variousfields (e.g., number of bits, location of bits) to specify, among otherthings, the operation to be performed (e.g., opcode) and the operand(s)on which that operation is to be performed and/or other data field(s)(e.g., mask). Some instruction formats are further broken down thoughthe definition of instruction templates (or subformats). For example,the instruction templates of a given instruction format may be definedto have different subsets of the instruction format's fields (theincluded fields are typically in the same order, but at least some havedifferent bit positions because there are less fields included) and/ordefined to have a given field interpreted differently. Thus, eachinstruction of an ISA is expressed using a given instruction format(and, if defined, in a given one of the instruction templates of thatinstruction format) and includes fields for specifying the operation andthe operands. For example, an exemplary ADD instruction has a specificopcode and an instruction format that includes an opcode field tospecify that opcode and operand fields to select operands(source1/destination and source2); and an occurrence of this ADDinstruction in an instruction stream will have specific contents in theoperand fields that select specific operands. A set of SIMD extensionsreferred to as the Advanced Vector Extensions (AVX) (AVX1 and AVX2) andusing the Vector Extensions (VEX) coding scheme has been released and/orpublished (e.g., see Intel® 64 and IA-32 Architectures SoftwareDeveloper's Manual, June 2016; and see Intel® Architecture InstructionSet Extensions Programming Reference, February 2016).

Exemplary Instruction Formats

Embodiments of the instruction(s) described herein may be embodied indifferent formats. Additionally, exemplary systems, architectures, andpipelines are detailed below. Embodiments of the instruction(s) may beexecuted on such systems, architectures, and pipelines, but are notlimited to those detailed.

Generic Vector Friendly Instruction Format

A vector friendly instruction format is an instruction format that issuited for vector instructions (e.g., there are certain fields specificto vector operations). While embodiments are described in which bothvector and scalar operations are supported through the vector friendlyinstruction format, alternative embodiments use only vector operationsthe vector friendly instruction format.

FIGS. 75A-75B are block diagrams illustrating a generic vector friendlyinstruction format and instruction templates thereof according toembodiments of the disclosure. FIG. 75A is a block diagram illustratinga generic vector friendly instruction format and class A instructiontemplates thereof according to embodiments of the disclosure; while FIG.75B is a block diagram illustrating the generic vector friendlyinstruction format and class B instruction templates thereof accordingto embodiments of the disclosure. Specifically, a generic vectorfriendly instruction format 7500 for which are defined class A and classB instruction templates, both of which include no memory access 7505instruction templates and memory access 7520 instruction templates. Theterm generic in the context of the vector friendly instruction formatrefers to the instruction format not being tied to any specificinstruction set.

While embodiments of the disclosure will be described in which thevector friendly instruction format supports the following: a 64 bytevector operand length (or size) with 32 bit (4 byte) or 64 bit (8 byte)data element widths (or sizes) (and thus, a 64 byte vector consists ofeither 16 doubleword-size elements or alternatively, 8 quadword-sizeelements); a 64 byte vector operand length (or size) with 16 bit (2byte) or 8 bit (1 byte) data element widths (or sizes); a 32 byte vectoroperand length (or size) with 32 bit (4 byte), 64 bit (8 byte), 16 bit(2 byte), or 8 bit (1 byte) data element widths (or sizes); and a 16byte vector operand length (or size) with 32 bit (4 byte), 64 bit (8byte), 16 bit (2 byte), or 8 bit (1 byte) data element widths (orsizes); alternative embodiments may support more, less and/or differentvector operand sizes (e.g., 256 byte vector operands) with more, less,or different data element widths (e.g., 128 bit (16 byte) data elementwidths).

The class A instruction templates in FIG. 75A include: 1) within the nomemory access 7505 instruction templates there is shown a no memoryaccess, full round control type operation 7510 instruction template anda no memory access, data transform type operation 7515 instructiontemplate; and 2) within the memory access 7520 instruction templatesthere is shown a memory access, temporal 7525 instruction template and amemory access, non-temporal 7530 instruction template. The class Binstruction templates in FIG. 75B include: 1) within the no memoryaccess 7505 instruction templates there is shown a no memory access,write mask control, partial round control type operation 7512instruction template and a no memory access, write mask control, vsizetype operation 7517 instruction template; and 2) within the memoryaccess 7520 instruction templates there is shown a memory access, writemask control 7527 instruction template.

The generic vector friendly instruction format 7500 includes thefollowing fields listed below in the order illustrated in FIGS. 75A-75B.

Format field 7540—a specific value (an instruction format identifiervalue) in this field uniquely identifies the vector friendly instructionformat, and thus occurrences of instructions in the vector friendlyinstruction format in instruction streams. As such, this field isoptional in the sense that it is not needed for an instruction set thathas only the generic vector friendly instruction format.

Base operation field 7542—its content distinguishes different baseoperations.

Register index field 7544—its content, directly or through addressgeneration, specifies the locations of the source and destinationoperands, be they in registers or in memory. These include a sufficientnumber of bits to select N registers from a P×Q (e.g. 32×512, 16×128,32×1024, 64×1024) register file. While in one embodiment N may be up tothree sources and one destination register, alternative embodiments maysupport more or less sources and destination registers (e.g., maysupport up to two sources where one of these sources also acts as thedestination, may support up to three sources where one of these sourcesalso acts as the destination, may support up to two sources and onedestination).

Modifier field 7546—its content distinguishes occurrences ofinstructions in the generic vector instruction format that specifymemory access from those that do not; that is, between no memory access7505 instruction templates and memory access 7520 instruction templates.Memory access operations read and/or write to the memory hierarchy (insome cases specifying the source and/or destination addresses usingvalues in registers), while non-memory access operations do not (e.g.,the source and destinations are registers). While in one embodiment thisfield also selects between three different ways to perform memoryaddress calculations, alternative embodiments may support more, less, ordifferent ways to perform memory address calculations.

Augmentation operation field 7550—its content distinguishes which one ofa variety of different operations to be performed in addition to thebase operation. This field is context specific. In one embodiment of thedisclosure, this field is divided into a class field 7568, an alphafield 7552, and a beta field 7554. The augmentation operation field 7550allows common groups of operations to be performed in a singleinstruction rather than 2, 3, or 4 instructions.

Scale field 7560—its content allows for the scaling of the index field'scontent for memory address generation (e.g., for address generation thatuses 2^(scale)*index+base).

Displacement Field 7562A—its content is used as part of memory addressgeneration (e.g., for address generation that uses2^(scale)*index+base+displacement).

Displacement Factor Field 7562B (note that the juxtaposition ofdisplacement field 7562A directly over displacement factor field 7562Bindicates one or the other is used)—its content is used as part ofaddress generation; it specifies a displacement factor that is to bescaled by the size of a memory access (N)—where N is the number of bytesin the memory access (e.g., for address generation that uses2^(scale)*index+base+scaled displacement). Redundant low-order bits areignored and hence, the displacement factor field's content is multipliedby the memory operands total size (N) in order to generate the finaldisplacement to be used in calculating an effective address. The valueof N is determined by the processor hardware at runtime based on thefull opcode field 7574 (described later herein) and the datamanipulation field 7554C. The displacement field 7562A and thedisplacement factor field 7562B are optional in the sense that they arenot used for the no memory access 7505 instruction templates and/ordifferent embodiments may implement only one or none of the two.

Data element width field 7564—its content distinguishes which one of anumber of data element widths is to be used (in some embodiments for allinstructions; in other embodiments for only some of the instructions).This field is optional in the sense that it is not needed if only onedata element width is supported and/or data element widths are supportedusing some aspect of the opcodes.

Write mask field 7570—its content controls, on a per data elementposition basis, whether that data element position in the destinationvector operand reflects the result of the base operation andaugmentation operation. Class A instruction templates supportmerging-writemasking, while class B instruction templates support bothmerging- and zeroing-writemasking. When merging, vector masks allow anyset of elements in the destination to be protected from updates duringthe execution of any operation (specified by the base operation and theaugmentation operation); in other one embodiment, preserving the oldvalue of each element of the destination where the corresponding maskbit has a 0. In contrast, when zeroing vector masks allow any set ofelements in the destination to be zeroed during the execution of anyoperation (specified by the base operation and the augmentationoperation); in one embodiment, an element of the destination is set to 0when the corresponding mask bit has a 0 value. A subset of thisfunctionality is the ability to control the vector length of theoperation being performed (that is, the span of elements being modified,from the first to the last one); however, it is not necessary that theelements that are modified be consecutive. Thus, the write mask field7570 allows for partial vector operations, including loads, stores,arithmetic, logical, etc. While embodiments of the disclosure aredescribed in which the write mask field's 7570 content selects one of anumber of write mask registers that contains the write mask to be used(and thus the write mask field's 7570 content indirectly identifies thatmasking to be performed), alternative embodiments instead or additionalallow the mask write field's 7570 content to directly specify themasking to be performed.

Immediate field 7572—its content allows for the specification of animmediate. This field is optional in the sense that is it not present inan implementation of the generic vector friendly format that does notsupport immediate and it is not present in instructions that do not usean immediate.

Class field 7568—its content distinguishes between different classes ofinstructions. With reference to FIGS. 75A-B, the contents of this fieldselect between class A and class B instructions. In FIGS. 75A-B, roundedcorner squares are used to indicate a specific value is present in afield (e.g., class A 7568A and class B 7568B for the class field 7568respectively in FIGS. 75A-B).

Instruction Templates of Class A

In the case of the non-memory access 7505 instruction templates of classA, the alpha field 7552 is interpreted as an RS field 7552A, whosecontent distinguishes which one of the different augmentation operationtypes are to be performed (e.g., round 7552A.1 and data transform7552A.2 are respectively specified for the no memory access, round typeoperation 7510 and the no memory access, data transform type operation7515 instruction templates), while the beta field 7554 distinguisheswhich of the operations of the specified type is to be performed. In theno memory access 7505 instruction templates, the scale field 7560, thedisplacement field 7562A, and the displacement scale filed 7562B are notpresent.

No-Memory Access Instruction Templates—Full Round Control Type Operation

In the no memory access full round control type operation 7510instruction template, the beta field 7554 is interpreted as a roundcontrol field 7554A, whose content(s) provide static rounding. While inthe described embodiments of the disclosure the round control field7554A includes a suppress all floating point exceptions (SAE) field 7556and a round operation control field 7558, alternative embodiments maysupport may encode both these concepts into the same field or only haveone or the other of these concepts/fields (e.g., may have only the roundoperation control field 7558).

SAE field 7556—its content distinguishes whether or not to disable theexception event reporting; when the SAE field's 7556 content indicatessuppression is enabled, a given instruction does not report any kind offloating-point exception flag and does not raise any floating pointexception handler.

Round operation control field 7558—its content distinguishes which oneof a group of rounding operations to perform (e.g., Round-up,Round-down, Round-towards-zero and Round-to-nearest). Thus, the roundoperation control field 7558 allows for the changing of the roundingmode on a per instruction basis. In one embodiment of the disclosurewhere a processor includes a control register for specifying roundingmodes, the round operation control field's 7550 content overrides thatregister value.

No Memory Access Instruction Templates—Data Transform Type Operation

In the no memory access data transform type operation 7515 instructiontemplate, the beta field 7554 is interpreted as a data transform field7554B, whose content distinguishes which one of a number of datatransforms is to be performed (e.g., no data transform, swizzle,broadcast).

In the case of a memory access 7520 instruction template of class A, thealpha field 7552 is interpreted as an eviction hint field 7552B, whosecontent distinguishes which one of the eviction hints is to be used (inFIG. 75A, temporal 7552B.1 and non-temporal 7552B.2 are respectivelyspecified for the memory access, temporal 7525 instruction template andthe memory access, non-temporal 7530 instruction template), while thebeta field 7554 is interpreted as a data manipulation field 7554C, whosecontent distinguishes which one of a number of data manipulationoperations (also known as primitives) is to be performed (e.g., nomanipulation; broadcast; up conversion of a source; and down conversionof a destination). The memory access 7520 instruction templates includethe scale field 7560, and optionally the displacement field 7562A or thedisplacement scale field 7562B.

Vector memory instructions perform vector loads from and vector storesto memory, with conversion support. As with regular vector instructions,vector memory instructions transfer data from/to memory in a dataelement-wise fashion, with the elements that are actually transferred isdictated by the contents of the vector mask that is selected as thewrite mask.

Memory Access Instruction Templates—Temporal

Temporal data is data likely to be reused soon enough to benefit fromcaching. This is, however, a hint, and different processors mayimplement it in different ways, including ignoring the hint entirely.

Memory Access Instruction Templates—Non-Temporal

Non-temporal data is data unlikely to be reused soon enough to benefitfrom caching in the 1st-level cache and should be given priority foreviction. This is, however, a hint, and different processors mayimplement it in different ways, including ignoring the hint entirely.

Instruction Templates of Class B

In the case of the instruction templates of class B, the alpha field7552 is interpreted as a write mask control (Z) field 7552C, whosecontent distinguishes whether the write masking controlled by the writemask field 7570 should be a merging or a zeroing.

In the case of the non-memory access 7505 instruction templates of classB, part of the beta field 7554 is interpreted as an RL field 7557A,whose content distinguishes which one of the different augmentationoperation types are to be performed (e.g., round 7557A.1 and vectorlength (VSIZE) 7557A.2 are respectively specified for the no memoryaccess, write mask control, partial round control type operation 7512instruction template and the no memory access, write mask control, VSIZEtype operation 7517 instruction template), while the rest of the betafield 7554 distinguishes which of the operations of the specified typeis to be performed. In the no memory access 7505 instruction templates,the scale field 7560, the displacement field 7562A, and the displacementscale filed 7562B are not present.

In the no memory access, write mask control, partial round control typeoperation 7510 instruction template, the rest of the beta field 7554 isinterpreted as a round operation field 7559A and exception eventreporting is disabled (a given instruction does not report any kind offloating-point exception flag and does not raise any floating pointexception handler).

Round operation control field 7559A—just as round operation controlfield 7558, its content distinguishes which one of a group of roundingoperations to perform (e.g., Round-up, Round-down, Round-towards-zeroand Round-to-nearest). Thus, the round operation control field 7559Aallows for the changing of the rounding mode on a per instruction basis.In one embodiment of the disclosure where a processor includes a controlregister for specifying rounding modes, the round operation controlfield's 7550 content overrides that register value.

In the no memory access, write mask control, VSIZE type operation 7517instruction template, the rest of the beta field 7554 is interpreted asa vector length field 7559B, whose content distinguishes which one of anumber of data vector lengths is to be performed on (e.g., 128, 256, or512 byte).

In the case of a memory access 7520 instruction template of class B,part of the beta field 7554 is interpreted as a broadcast field 7557B,whose content distinguishes whether or not the broadcast type datamanipulation operation is to be performed, while the rest of the betafield 7554 is interpreted the vector length field 7559B. The memoryaccess 7520 instruction templates include the scale field 7560, andoptionally the displacement field 7562A or the displacement scale field7562B.

With regard to the generic vector friendly instruction format 7500, afull opcode field 7574 is shown including the format field 7540, thebase operation field 7542, and the data element width field 7564. Whileone embodiment is shown where the full opcode field 7574 includes all ofthese fields, the full opcode field 7574 includes less than all of thesefields in embodiments that do not support all of them. The full opcodefield 7574 provides the operation code (opcode).

The augmentation operation field 7550, the data element width field7564, and the write mask field 7570 allow these features to be specifiedon a per instruction basis in the generic vector friendly instructionformat.

The combination of write mask field and data element width field createtyped instructions in that they allow the mask to be applied based ondifferent data element widths.

The various instruction templates found within class A and class B arebeneficial in different situations. In some embodiments of thedisclosure, different processors or different cores within a processormay support only class A, only class B, or both classes. For instance, ahigh performance general purpose out-of-order core intended forgeneral-purpose computing may support only class B, a core intendedprimarily for graphics and/or scientific (throughput) computing maysupport only class A, and a core intended for both may support both (ofcourse, a core that has some mix of templates and instructions from bothclasses but not all templates and instructions from both classes iswithin the purview of the disclosure). Also, a single processor mayinclude multiple cores, all of which support the same class or in whichdifferent cores support different class. For instance, in a processorwith separate graphics and general purpose cores, one of the graphicscores intended primarily for graphics and/or scientific computing maysupport only class A, while one or more of the general purpose cores maybe high performance general purpose cores with out of order executionand register renaming intended for general-purpose computing thatsupport only class B. Another processor that does not have a separategraphics core, may include one more general purpose in-order orout-of-order cores that support both class A and class B. Of course,features from one class may also be implement in the other class indifferent embodiments of the disclosure. Programs written in a highlevel language would be put (e.g., just in time compiled or staticallycompiled) into an variety of different executable forms, including: 1) aform having only instructions of the class(es) supported by the targetprocessor for execution; or 2) a form having alternative routineswritten using different combinations of the instructions of all classesand having control flow code that selects the routines to execute basedon the instructions supported by the processor which is currentlyexecuting the code.

Exemplary Specific Vector Friendly Instruction Format

FIG. 76 is a block diagram illustrating an exemplary specific vectorfriendly instruction format according to embodiments of the disclosure.FIG. 76 shows a specific vector friendly instruction format 7600 that isspecific in the sense that it specifies the location, size,interpretation, and order of the fields, as well as values for some ofthose fields. The specific vector friendly instruction format 7600 maybe used to extend the x86 instruction set, and thus some of the fieldsare similar or the same as those used in the existing x86 instructionset and extension thereof (e.g., AVX). This format remains consistentwith the prefix encoding field, real opcode byte field, MOD R/M field,SIB field, displacement field, and immediate fields of the existing x86instruction set with extensions. The fields from FIG. 75 into which thefields from FIG. 76 map are illustrated.

It should be understood that, although embodiments of the disclosure aredescribed with reference to the specific vector friendly instructionformat 7600 in the context of the generic vector friendly instructionformat 7500 for illustrative purposes, the disclosure is not limited tothe specific vector friendly instruction format 7600 except whereclaimed. For example, the generic vector friendly instruction format7500 contemplates a variety of possible sizes for the various fields,while the specific vector friendly instruction format 7600 is shown ashaving fields of specific sizes. By way of specific example, while thedata element width field 7564 is illustrated as a one bit field in thespecific vector friendly instruction format 7600, the disclosure is notso limited (that is, the generic vector friendly instruction format 7500contemplates other sizes of the data element width field 7564).

The generic vector friendly instruction format 7500 includes thefollowing fields listed below in the order illustrated in FIG. 76A.

EVEX Prefix (Bytes 0-3) 7602—is encoded in a four-byte form.

Format Field 7540 (EVEX Byte 0, bits [7:0])—the first byte (EVEX Byte 0)is the format field 7540 and it contains 0x62 (the unique value used fordistinguishing the vector friendly instruction format in one embodimentof the disclosure).

The second-fourth bytes (EVEX Bytes 1-3) include a number of bit fieldsproviding specific capability.

REX field 7605 (EVEX Byte 1, bits [7-5])—consists of a EVEX.R bit field(EVEX Byte 1, bit [7]—R), EVEX.X bit field (EVEX byte 1, bit [6]—X), and7557BEX byte 1, bit[5]—B). The EVEX.R, EVEX.X, and EVEX.B bit fieldsprovide the same functionality as the corresponding VEX bit fields, andare encoded using is complement form, i.e. ZMM0 is encoded as 1111B,ZMM15 is encoded as 0000B. Other fields of the instructions encode thelower three bits of the register indexes as is known in the art (rrr,xxx, and bbb), so that Rrrr, Xxxx, and Bbbb may be formed by addingEVEX.R, EVEX.X, and EVEX.B.

REX′ field 7510—this is the first part of the REX′ field 7510 and is theEVEX.R′ bit field (EVEX Byte 1, bit [4]—R′) that is used to encodeeither the upper 16 or lower 16 of the extended 32 register set. In oneembodiment of the disclosure, this bit, along with others as indicatedbelow, is stored in bit inverted format to distinguish (in thewell-known x86 32-bit mode) from the BOUND instruction, whose realopcode byte is 62, but does not accept in the MOD RIM field (describedbelow) the value of 11 in the MOD field; alternative embodiments of thedisclosure do not store this and the other indicated bits below in theinverted format. A value of 1 is used to encode the lower 16 registers.In other words, R′Rrrr is formed by combining EVEX.R′, EVEX.R, and theother RRR from other fields.

Opcode map field 7615 (EVEX byte 1, bits [3:0]—mmmm)—its content encodesan implied leading opcode byte (0F, 0F 38, or 0F 3).

Data element width field 7564 (EVEX byte 2, bit [7]—W)—is represented bythe notation EVEX.W. EVEX.W is used to define the granularity (size) ofthe datatype (either 32-bit data elements or 64-bit data elements).

EVEX.vvvv 7620 (EVEX Byte 2, bits [6:3]—vvvv)—the role of EVEX.vvvv mayinclude the following: 1) EVEX.vvvv encodes the first source registeroperand, specified in inverted (1s complement) form and is valid forinstructions with 2 or more source operands; 2) EVEX.vvvv encodes thedestination register operand, specified in 1s complement form forcertain vector shifts; or 3) EVEX.vvvv does not encode any operand, thefield is reserved and should contain 1111b. Thus, EVEX.vvvv field 7620encodes the 4 low-order bits of the first source register specifierstored in inverted (1s complement) form. Depending on the instruction,an extra different EVEX bit field is used to extend the specifier sizeto 32 registers.

EVEX.U 7568 Class field (EVEX byte 2, bit [2]—U)—If EVEX.U=0, itindicates class A or EVEX.U0; if EVEX.U=1, it indicates class B orEVEX.U1.

Prefix encoding field 7625 (EVEX byte 2, bits [1:0]—pp)—providesadditional bits for the base operation field. In addition to providingsupport for the legacy SSE instructions in the EVEX prefix format, thisalso has the benefit of compacting the SIMD prefix (rather thanrequiring a byte to express the SIMD prefix, the EVEX prefix requiresonly 2 bits). In one embodiment, to support legacy SSE instructions thatuse a SIMD prefix (66H, F2H, F3H) in both the legacy format and in theEVEX prefix format, these legacy SIMD prefixes are encoded into the SIMDprefix encoding field; and at runtime are expanded into the legacy SIMDprefix prior to being provided to the decoder's PLA (so the PLA canexecute both the legacy and EVEX format of these legacy instructionswithout modification). Although newer instructions could use the EVEXprefix encoding field's content directly as an opcode extension, certainembodiments expand in a similar fashion for consistency but allow fordifferent meanings to be specified by these legacy SIMD prefixes. Analternative embodiment may redesign the PLA to support the 2 bit SIMDprefix encodings, and thus not require the expansion.

Alpha field 7552 (EVEX byte 3, bit [7]—EH; also known as EVEX.EH,EVEX.rs, EVEX.RL, EVEX.write mask control, and EVEX.N; also illustratedwith α)—as previously described, this field is context specific.

Beta field 7554 (EVEX byte 3, bits [6:4]—SSS, also known as EVEX.s₂₋₀,EVEX.r₂₋₀, EVEX.rr1, EVEX.LL0, EVEX.LLB; also illustrated with βββ)—aspreviously described, this field is context specific.

REX′ field 7510—this is the remainder of the REX′ field and is theEVEX.V′ bit field (EVEX Byte 3, bit [3]—V′) that may be used to encodeeither the upper 16 or lower 16 of the extended 32 register set. Thisbit is stored in bit inverted format. A value of 1 is used to encode thelower 16 registers. In other words, V′VVVV is formed by combiningEVEX.V′, EVEX.vvvv.

Write mask field 7570 (EVEX byte 3, bits [2:0]-kkk)—its contentspecifies the index of a register in the write mask registers aspreviously described. In one embodiment of the disclosure, the specificvalue EVEX kkk=000 has a special behavior implying no write mask is usedfor the particular instruction (this may be implemented in a variety ofways including the use of a write mask hardwired to all ones or hardwarethat bypasses the masking hardware).

Real Opcode Field 7630 (Byte 4) is also known as the opcode byte. Partof the opcode is specified in this field.

MOD R/M Field 7640 (Byte 5) includes MOD field 7642, Reg field 7644, andR/M field 7646. As previously described, the MOD field's 7642 contentdistinguishes between memory access and non-memory access operations.The role of Reg field 7644 can be summarized to two situations: encodingeither the destination register operand or a source register operand, orbe treated as an opcode extension and not used to encode any instructionoperand. The role of R/M field 7646 may include the following: encodingthe instruction operand that references a memory address, or encodingeither the destination register operand or a source register operand.

Scale, Index, Base (SIB) Byte (Byte 6)—As previously described, thescale field's 5450 content is used for memory address generation.SIB.xxx 7654 and SIB.bbb 7656—the contents of these fields have beenpreviously referred to with regard to the register indexes Xxxx andBbbb.

Displacement field 7562A (Bytes 7-10)—when MOD field 7642 contains 10,bytes 7-10 are the displacement field7562A, and it works the same as thelegacy 32-bit displacement (disp32) and works at byte granularity.

Displacement factor field7562B (Byte 7)—when MOD field 7642 contains 01,byte 7 is the displacement factor field7562B. The location of this fieldis that same as that of the legacy x86 instruction set 8-bitdisplacement (disp8), which works at byte granularity. Since disp8 issign extended, it can only address between −128 and 127 bytes offsets;in terms of 64 byte cache lines, disp8 uses 8 bits that can be set toonly four really useful values −128, −64, 0, and 64; since a greaterrange is often needed, disp32 is used; however, disp32 requires 4 bytes.In contrast to disp8 and disp32, the displacement factor field7562B is areinterpretation of disp8; when using displacement factor field7562B,the actual displacement is determined by the content of the displacementfactor field multiplied by the size of the memory operand access (N).This type of displacement is referred to as disp8*N. This reduces theaverage instruction length (a single byte of used for the displacementbut with a much greater range). Such compressed displacement is based onthe assumption that the effective displacement is multiple of thegranularity of the memory access, and hence, the redundant low-orderbits of the address offset do not need to be encoded. In other words,the displacement factor field7562B substitutes the legacy x86instruction set 8-bit displacement. Thus, the displacement factorfield7562B is encoded the same way as an x86 instruction set 8-bitdisplacement (so no changes in the ModRM/SIB encoding rules) with theonly exception that disp8 is overloaded to disp8*N. In other words,there are no changes in the encoding rules or encoding lengths but onlyin the interpretation of the displacement value by hardware (which needsto scale the displacement by the size of the memory operand to obtain abyte-wise address offset). Immediate field7572 operates as previouslydescribed.

Full Opcode Field

FIG. 76B is a block diagram illustrating the fields of the specificvector friendly instruction format 7600 that make up the full opcodefield7574 according to one embodiment of the disclosure. Specifically,the full opcode field7574 includes the format field 7540, the baseoperation field 7542, and the data element width (W) field 7564. Thebase operation field 7542 includes the prefix encoding field 7625, theopcode map field 7615, and the real opcode field 7630.

Register Index Field

FIG. 76C is a block diagram illustrating the fields of the specificvector friendly instruction format 7600 that make up the register indexfield 7544 according to one embodiment of the disclosure. Specifically,the register index field 7544 includes the REX field 7605, the REX′field 7610, the MODR/M.reg field 7644, the MODR/M.r/m field 7646, theVVVV field 7620, xxx field 7654, and the bbb field 7656.

Augmentation Operation Field

FIG. 76D is a block diagram illustrating the fields of the specificvector friendly instruction format 7600 that make up the augmentationoperation field 7550 according to one embodiment of the disclosure. Whenthe class (U) field 7568 contains 0, it signifies EVEX.U0 (class A7568A); when it contains 1, it signifies EVEX.U1 (class B 7568B). WhenU=0 and the MOD field 7642 contains 11 (signifying a no memory accessoperation), the alpha field 7552 (EVEX byte 3, bit [7]—EH) isinterpreted as the rs field 7552A. When the rs field 7552A contains a 1(round 7552A.1), the beta field 7554 (EVEX byte 3, bits [6:4]—SSS) isinterpreted as the round control field 7554A. The round control field7554A includes a one bit SAE field 7556 and a two bit round operationfield 7558. When the rs field 7552A contains a 0 (data transform7552A.2), the beta field 7554 (EVEX byte 3, bits [6:4]—SSS) isinterpreted as a three bit data transform field 7554B. When U=0 and theMOD field 7642 contains 00, 01, or 10 (signifying a memory accessoperation), the alpha field 7552 (EVEX byte 3, bit [7]—EH) isinterpreted as the eviction hint (EH) field 7552B and the beta field7554 (EVEX byte 3, bits [6:4]—SSS) is interpreted as a three bit datamanipulation field 7554C.

When U=1, the alpha field 7552 (EVEX byte 3, bit [7]—EH) is interpretedas the write mask control (Z) field 7552C. When U=1 and the MOD field7642 contains 11 (signifying a no memory access operation), part of thebeta field 7554 (EVEX byte 3, bit [4]—S₀) is interpreted as the RL field7557A; when it contains a 1 (round 7557A.1) the rest of the beta field7554 (EVEX byte 3, bit [6-5]—S₂₋₁) is interpreted as the round operationfield 7559A, while when the RL field 7557A contains a 0 (VSIZE 7557.A2)the rest of the beta field 7554 (EVEX byte 3, bit [6-5]—S₂₋₁) isinterpreted as the vector length field 7559B (EVEX byte 3, bit[6-5]—L₁₋₀). When U=1 and the MOD field 7642 contains 00, 01, or 10(signifying a memory access operation), the beta field 7554 (EVEX byte3, bits [6:4]—SSS) is interpreted as the vector length field 7559B (EVEXbyte 3, bit [6-5]—L₁₋₀) and the broadcast field 7557B (EVEX byte 3, bit[4]-B).

Exemplary Register Architecture

FIG. 77 is a block diagram of a register architecture 7700 according toone embodiment of the disclosure. In the embodiment illustrated, thereare 32 vector registers 7710 that are 512 bits wide; these registers arereferenced as zmm0 through zmm31. The lower order 256 bits of the lower16 zmm registers are overlaid on registers ymm0-16. The lower order 128bits of the lower 16 zmm registers (the lower order 128 bits of the ymmregisters) are overlaid on registers xmm0-15. The specific vectorfriendly instruction format 7600 operates on these overlaid registerfile as illustrated in the below tables.

Adjustable Vector Length Class Operations Registers InstructionTemplates A (FIG. 75A; 5410, 7515, zmm registers (the vector that do notinclude the U = 0) 7525, 7530 length is 64 byte) vector length field B(FIG. 75B; 5412 zmm registers (the vector 7559B U = 1) length is 64byte) Instruction templates B (FIG. 75B; 5417, 7527 zmm, ymm, or xmmregisters that do include the U = 1) (the vector length is 64 vectorlength field byte, 32 byte, or 16 7559B byte) depending on the vectorlength field 7559B

In other words, the vector length field 7559B selects between a maximumlength and one or more other shorter lengths, where each such shorterlength is half the length of the preceding length; and instructionstemplates without the vector length field 7559B operate on the maximumvector length. Further, in one embodiment, the class B instructiontemplates of the specific vector friendly instruction format 7600operate on packed or scalar single/double-precision floating point dataand packed or scalar integer data. Scalar operations are operationsperformed on the lowest order data element position in an zmm/ymm/xmmregister; the higher order data element positions are either left thesame as they were prior to the instruction or zeroed depending on theembodiment.

Write mask registers 7715—in the embodiment illustrated, there are 8write mask registers (k0 through k7), each 64 bits in size. In analternate embodiment, the write mask registers 7715 are 16 bits in size.As previously described, in one embodiment of the disclosure, the vectormask register k0 cannot be used as a write mask; when the encoding thatwould normally indicate k0 is used for a write mask, it selects ahardwired write mask of 0xFFFF, effectively disabling write masking forthat instruction.

General-purpose registers 7725—in the embodiment illustrated, there aresixteen 64-bit general-purpose registers that are used along with theexisting x86 addressing modes to address memory operands. Theseregisters are referenced by the names RAX, RBX, RCX, RDX, RBP, RSI, RDI,RSP, and R8 through R15.

Scalar floating point stack register file (x87 stack) 7745, on which isaliased the MMX packed integer flat register file 7750—in the embodimentillustrated, the x87 stack is an eight-element stack used to performscalar floating-point operations on 32/64/80-bit floating point datausing the x87 instruction set extension; while the MMX registers areused to perform operations on 64-bit packed integer data, as well as tohold operands for some operations performed between the MMX and XMMregisters.

Alternative embodiments of the disclosure may use wider or narrowerregisters. Additionally, alternative embodiments of the disclosure mayuse more, less, or different register files and registers.

Exemplary Core Architectures, Processors, and Computer Architectures

Processor cores may be implemented in different ways, for differentpurposes, and in different processors. For instance, implementations ofsuch cores may include: 1) a general purpose in-order core intended forgeneral-purpose computing; 2) a high performance general purposeout-of-order core intended for general-purpose computing; 3) a specialpurpose core intended primarily for graphics and/or scientific(throughput) computing. Implementations of different processors mayinclude: 1) a CPU including one or more general purpose in-order coresintended for general-purpose computing and/or one or more generalpurpose out-of-order cores intended for general-purpose computing; and2) a coprocessor including one or more special purpose cores intendedprimarily for graphics and/or scientific (throughput). Such differentprocessors lead to different computer system architectures, which mayinclude: 1) the coprocessor on a separate chip from the CPU; 2) thecoprocessor on a separate die in the same package as a CPU; 3) thecoprocessor on the same die as a CPU (in which case, such a coprocessoris sometimes referred to as special purpose logic, such as integratedgraphics and/or scientific (throughput) logic, or as special purposecores); and 4) a system on a chip that may include on the same die thedescribed CPU (sometimes referred to as the application core(s) orapplication processor(s)), the above described coprocessor, andadditional functionality. Exemplary core architectures are describednext, followed by descriptions of exemplary processors and computerarchitectures.

Exemplary Core Architectures In-Order and Out-of-Order Core BlockDiagram

FIG. 78A is a block diagram illustrating both an exemplary in-orderpipeline and an exemplary register renaming, out-of-orderissue/execution pipeline according to embodiments of the disclosure.FIG. 78B is a block diagram illustrating both an exemplary embodiment ofan in-order architecture core and an exemplary register renaming,out-of-order issue/execution architecture core to be included in aprocessor according to embodiments of the disclosure. The solid linedboxes in FIGS. 78A-B illustrate the in-order pipeline and in-order core,while the optional addition of the dashed lined boxes illustrates theregister renaming, out-of-order issue/execution pipeline and core. Giventhat the in-order aspect is a subset of the out-of-order aspect, theout-of-order aspect will be described.

In FIG. 78A, a processor pipeline 7800 includes a fetch stage 7802, alength decode stage 7804, a decode stage 7806, an allocation stage 7808,a renaming stage 7810, a scheduling (also known as a dispatch or issue)stage 7812, a register read/memory read stage 7814, an execute stage7816, a write back/memory write stage 7818, an exception handling stage7822, and a commit stage 7824.

FIG. 78B shows processor core 7890 including a front end unit 7830coupled to an execution engine unit 7850, and both are coupled to amemory unit 7870. The core 7890 may be a reduced instruction setcomputing (RISC) core, a complex instruction set computing (CISC) core,a very long instruction word (VLIW) core, or a hybrid or alternativecore type. As yet another option, the core 7890 may be a special-purposecore, such as, for example, a network or communication core, compressionengine, coprocessor core, general purpose computing graphics processingunit (GPGPU) core, graphics core, or the like.

The front end unit 7830 includes a branch prediction unit 7832 coupledto an instruction cache unit 7834, which is coupled to an instructiontranslation lookaside buffer (TLB) 7836, which is coupled to aninstruction fetch unit 7838, which is coupled to a decode unit 7840. Thedecode unit 7840 (or decoder or decoder unit) may decode instructions(e.g., macro-instructions), and generate as an output one or moremicro-operations, micro-code entry points, micro-instructions, otherinstructions, or other control signals, which are decoded from, or whichotherwise reflect, or are derived from, the original instructions. Thedecode unit 7840 may be implemented using various different mechanisms.Examples of suitable mechanisms include, but are not limited to, look-uptables, hardware implementations, programmable logic arrays (PLAs),microcode read only memories (ROMs), etc. In one embodiment, the core7890 includes a microcode ROM or other medium that stores microcode forcertain macro-instructions (e.g., in decode unit 7840 or otherwisewithin the front end unit 7830). The decode unit 7840 is coupled to arename/allocator unit 7852 in the execution engine unit 7850.

The execution engine unit 7850 includes the rename/allocator unit 7852coupled to a retirement unit 7854 and a set of one or more schedulerunit(s) 7856. The scheduler unit(s) 7856 represents any number ofdifferent schedulers, including reservations stations, centralinstruction window, etc. The scheduler unit(s) 7856 is coupled to thephysical register file(s) unit(s) 7858. Each of the physical registerfile(s) units 7858 represents one or more physical register files,different ones of which store one or more different data types, such asscalar integer, scalar floating point, packed integer, packed floatingpoint, vector integer, vector floating point, status (e.g., aninstruction pointer that is the address of the next instruction to beexecuted), etc. In one embodiment, the physical register file(s) unit7858 comprises a vector registers unit, a write mask registers unit, anda scalar registers unit. These register units may provide architecturalvector registers, vector mask registers, and general purpose registers.The physical register file(s) unit(s) 7858 is overlapped by theretirement unit 7854 to illustrate various ways in which registerrenaming and out-of-order execution may be implemented (e.g., using areorder buffer(s) and a retirement register file(s); using a futurefile(s), a history buffer(s), and a retirement register file(s); using aregister maps and a pool of registers; etc.). The retirement unit 7854and the physical register file(s) unit(s) 7858 are coupled to theexecution cluster(s) 7860. The execution cluster(s) 7860 includes a setof one or more execution units 7862 and a set of one or more memoryaccess units 7864. The execution units 7862 may perform variousoperations (e.g., shifts, addition, subtraction, multiplication) and onvarious types of data (e.g., scalar floating point, packed integer,packed floating point, vector integer, vector floating point). Whilesome embodiments may include a number of execution units dedicated tospecific functions or sets of functions, other embodiments may includeonly one execution unit or multiple execution units that all perform allfunctions. The scheduler unit(s) 7856, physical register file(s) unit(s)7858, and execution cluster(s) 7860 are shown as being possibly pluralbecause certain embodiments create separate pipelines for certain typesof data/operations (e.g., a scalar integer pipeline, a scalar floatingpoint/packed integer/packed floating point/vector integer/vectorfloating point pipeline, and/or a memory access pipeline that each havetheir own scheduler unit, physical register file(s) unit, and/orexecution cluster—and in the case of a separate memory access pipeline,certain embodiments are implemented in which only the execution clusterof this pipeline has the memory access unit(s) 7864). It should also beunderstood that where separate pipelines are used, one or more of thesepipelines may be out-of-order issue/execution and the rest in-order.

The set of memory access units 7864 is coupled to the memory unit 7870,which includes a data TLB unit 7872 coupled to a data cache unit 7874coupled to a level 2 (L2) cache unit 7876. In one exemplary embodiment,the memory access units 7864 may include a load unit, a store addressunit, and a store data unit, each of which is coupled to the data TLBunit 7872 in the memory unit 7870. The instruction cache unit 7834 isfurther coupled to a level 2 (L2) cache unit 7876 in the memory unit7870. The L2 cache unit 7876 is coupled to one or more other levels ofcache and eventually to a main memory.

By way of example, the exemplary register renaming, out-of-orderissue/execution core architecture may implement the pipeline 7800 asfollows: 1) the instruction fetch 7838 performs the fetch and lengthdecoding stages 7802 and 7804; 2) the decode unit 7840 performs thedecode stage 7806; 3) the rename/allocator unit 7852 performs theallocation stage 7808 and renaming stage 7810; 4) the scheduler unit(s)7856 performs the schedule stage 7812; 5) the physical register file(s)unit(s) 7858 and the memory unit 7870 perform the register read/memoryread stage 7814; the execution cluster 7860 perform the execute stage7816; 6) the memory unit 7870 and the physical register file(s) unit(s)7858 perform the write back/memory write stage 7818; 7) various unitsmay be involved in the exception handling stage 7822; and 8) theretirement unit 7854 and the physical register file(s) unit(s) 7858perform the commit stage 7824.

The core 7890 may support one or more instructions sets (e.g., the x86instruction set (with some extensions that have been added with newerversions); the MIPS instruction set of MIPS Technologies of Sunnyvale,Calif.; the ARM instruction set (with optional additional extensionssuch as NEON) of ARM Holdings of Sunnyvale, Calif.), including theinstruction(s) described herein. In one embodiment, the core 7890includes logic to support a packed data instruction set extension (e.g.,AVX1, AVX2), thereby allowing the operations used by many multimediaapplications to be performed using packed data.

It should be understood that the core may support multithreading(executing two or more parallel sets of operations or threads), and maydo so in a variety of ways including time sliced multithreading,simultaneous multithreading (where a single physical core provides alogical core for each of the threads that physical core issimultaneously multithreading), or a combination thereof (e.g., timesliced fetching and decoding and simultaneous multithreading thereaftersuch as in the Intel® Hyperthreading technology).

While register renaming is described in the context of out-of-orderexecution, it should be understood that register renaming may be used inan in-order architecture. While the illustrated embodiment of theprocessor also includes separate instruction and data cache units7834/7874 and a shared L2 cache unit 7876, alternative embodiments mayhave a single internal cache for both instructions and data, such as,for example, a Level 1 (L1) internal cache, or multiple levels ofinternal cache. In some embodiments, the system may include acombination of an internal cache and an external cache that is externalto the core and/or the processor. Alternatively, all of the cache may beexternal to the core and/or the processor.

Specific Exemplary In-Order Core Architecture

FIGS. 79A-B illustrate a block diagram of a more specific exemplaryin-order core architecture, which core would be one of several logicblocks (including other cores of the same type and/or different types)in a chip. The logic blocks communicate through a high-bandwidthinterconnect network (e.g., a ring network) with some fixed functionlogic, memory I/O interfaces, and other necessary I/O logic, dependingon the application.

FIG. 79A is a block diagram of a single processor core, along with itsconnection to the on-die interconnect network 7902 and with its localsubset of the Level 2 (L2) cache 7904, according to embodiments of thedisclosure. In one embodiment, an instruction decode unit 7900 supportsthe x86 instruction set with a packed data instruction set extension. AnL1 cache 7906 allows low-latency accesses to cache memory into thescalar and vector units. While in one embodiment (to simplify thedesign), a scalar unit 7908 and a vector unit 7910 use separate registersets (respectively, scalar registers 7912 and vector registers 7914) anddata transferred between them is written to memory and then read back infrom a level 1 (L1) cache 7906, alternative embodiments of thedisclosure may use a different approach (e.g., use a single register setor include a communication path that allow data to be transferredbetween the two register files without being written and read back).

The local subset of the L2 cache 7904 is part of a global L2 cache thatis divided into separate local subsets, one per processor core. Eachprocessor core has a direct access path to its own local subset of theL2 cache 7904. Data read by a processor core is stored in its L2 cachesubset 7904 and can be accessed quickly, in parallel with otherprocessor cores accessing their own local L2 cache subsets. Data writtenby a processor core is stored in its own L2 cache subset 7904 and isflushed from other subsets, if necessary. The ring network ensurescoherency for shared data. The ring network is bi-directional to allowagents such as processor cores, hf caches and other logic blocks tocommunicate with each other within the chip. Each ring data-path is1012-bits wide per direction.

FIG. 79B is an expanded view of part of the processor core in FIG. 79Aaccording to embodiments of the disclosure. FIG. 79B includes an L1 datacache 7906A part of the L1 cache 7904, as well as more detail regardingthe vector unit 7910 and the vector registers 7914. Specifically, thevector unit 7910 is a 16-wide vector processing unit (VPU) (see the16-wide ALU 7928), which executes one or more of integer,single-precision float, and double-precision float instructions. The VPUsupports swizzling the register inputs with swizzle unit 7920, numericconversion with numeric convert units 7922A-B, and replication withreplication unit 7924 on the memory input. Write mask registers 7926allow predicating resulting vector writes.

FIG. 80 is a block diagram of a processor 8000 that may have more thanone core, may have an integrated memory controller, and may haveintegrated graphics according to embodiments of the disclosure. Thesolid lined boxes in FIG. 80 illustrate a processor 8000 with a singlecore 8002A, a system agent 8010, a set of one or more bus controllerunits 8016, while the optional addition of the dashed lined boxesillustrates an alternative processor 8000 with multiple cores 8002A-N, aset of one or more integrated memory controller unit(s) 8014 in thesystem agent unit 8010, and special purpose logic 8008.

Thus, different implementations of the processor 8000 may include: 1) aCPU with the special purpose logic 8008 being integrated graphics and/orscientific (throughput) logic (which may include one or more cores), andthe cores 8002A-N being one or more general purpose cores (e.g., generalpurpose in-order cores, general purpose out-of-order cores, acombination of the two); 2) a coprocessor with the cores 8002A-N being alarge number of special purpose cores intended primarily for graphicsand/or scientific (throughput); and 3) a coprocessor with the cores8002A-N being a large number of general purpose in-order cores. Thus,the processor 8000 may be a general-purpose processor, coprocessor orspecial-purpose processor, such as, for example, a network orcommunication processor, compression engine, graphics processor, GPGPU(general purpose graphics processing unit), a high-throughput manyintegrated core (MIC) coprocessor (including 30 or more cores), embeddedprocessor, or the like. The processor may be implemented on one or morechips. The processor 8000 may be a part of and/or may be implemented onone or more substrates using any of a number of process technologies,such as, for example, BiCMOS, CMOS, or NMOS.

The memory hierarchy includes one or more levels of cache within thecores, a set or one or more shared cache units 8006, and external memory(not shown) coupled to the set of integrated memory controller units8014. The set of shared cache units 8006 may include one or moremid-level caches, such as level 2 (L2), level 3 (L3), level 4 (L4), orother levels of cache, a last level cache (LLC), and/or combinationsthereof. While in one embodiment a ring based interconnect unit 8012interconnects the integrated graphics logic 8008, the set of sharedcache units 8006, and the system agent unit 8010/integrated memorycontroller unit(s) 8014, alternative embodiments may use any number ofwell-known techniques for interconnecting such units. In one embodiment,coherency is maintained between one or more cache units 8006 and cores8002-A-N.

In some embodiments, one or more of the cores 8002A-N are capable ofmulti-threading. The system agent 8010 includes those componentscoordinating and operating cores 8002A-N. The system agent unit 8010 mayinclude for example a power control unit (PCU) and a display unit. ThePCU may be or include logic and components needed for regulating thepower state of the cores 8002A-N and the integrated graphics logic 8008.The display unit is for driving one or more externally connecteddisplays.

The cores 8002A-N may be homogenous or heterogeneous in terms ofarchitecture instruction set; that is, two or more of the cores 8002A-Nmay be capable of execution the same instruction set, while others maybe capable of executing only a subset of that instruction set or adifferent instruction set.

Exemplary Computer Architectures

FIGS. 81-84 are block diagrams of exemplary computer architectures.Other system designs and configurations known in the arts for laptops,desktops, handheld PCs, personal digital assistants, engineeringworkstations, servers, network devices, network hubs, switches, embeddedprocessors, digital signal processors (DSPs), graphics devices, videogame devices, set-top boxes, micro controllers, cell phones, portablemedia players, hand held devices, and various other electronic devices,are also suitable. In general, a huge variety of systems or electronicdevices capable of incorporating a processor and/or other executionlogic as disclosed herein are generally suitable.

Referring now to FIG. 81, shown is a block diagram of a system 8100 inaccordance with one embodiment of the present disclosure. The system8100 may include one or more processors 8110, 8115, which are coupled toa controller hub 8120. In one embodiment the controller hub 8120includes a graphics memory controller hub (GMCH) 8190 and anInput/Output Hub (IOH) 8150 (which may be on separate chips); the GMCH8190 includes memory and graphics controllers to which are coupledmemory 8140 and a coprocessor 8145; the IOH 8150 is couples input/output(I/O) devices 8160 to the GMCH 8190. Alternatively, one or both of thememory and graphics controllers are integrated within the processor (asdescribed herein), the memory 8140 and the coprocessor 8145 are coupleddirectly to the processor 8110, and the controller hub 8120 in a singlechip with the IOH 8150. Memory 8140 may include a compiler module 8140A,for example, to store code that when executed causes a processor toperform any method of this disclosure.

The optional nature of additional processors 8115 is denoted in FIG. 81with broken lines. Each processor 8110, 8115 may include one or more ofthe processing cores described herein and may be some version of theprocessor 8000.

The memory 8140 may be, for example, dynamic random access memory(DRAM), phase change memory (PCM), or a combination of the two. For atleast one embodiment, the controller hub 8120 communicates with theprocessor(s) 8110, 8115 via a multi-drop bus, such as a frontside bus(FSB), point-to-point interface such as QuickPath Interconnect (QPI), orsimilar connection 8195.

In one embodiment, the coprocessor 8145 is a special-purpose processor,such as, for example, a high-throughput MIC processor, a network orcommunication processor, compression engine, graphics processor, GPGPU,embedded processor, or the like. In one embodiment, controller hub 8120may include an integrated graphics accelerator.

There can be a variety of differences between the physical resources8110, 8115 in terms of a spectrum of metrics of merit includingarchitectural, microarchitectural, thermal, power consumptioncharacteristics, and the like.

In one embodiment, the processor 8110 executes instructions that controldata processing operations of a general type. Embedded within theinstructions may be coprocessor instructions. The processor 8110recognizes these coprocessor instructions as being of a type that shouldbe executed by the attached coprocessor 8145. Accordingly, the processor8110 issues these coprocessor instructions (or control signalsrepresenting coprocessor instructions) on a coprocessor bus or otherinterconnect, to coprocessor 8145. Coprocessor(s) 8145 accept andexecute the received coprocessor instructions.

Referring now to FIG. 82, shown is a block diagram of a first morespecific exemplary system 8200 in accordance with an embodiment of thepresent disclosure. As shown in FIG. 82, multiprocessor system 8200 is apoint-to-point interconnect system, and includes a first processor 8270and a second processor 8280 coupled via a point-to-point interconnect8250. Each of processors 8270 and 8280 may be some version of theprocessor 8000. In one embodiment of the disclosure, processors 8270 and8280 are respectively processors 8110 and 8115, while coprocessor 8238is coprocessor 8145. In another embodiment, processors 8270 and 8280 arerespectively processor 8110 coprocessor 8145.

Processors 8270 and 8280 are shown including integrated memorycontroller (IMC) units 8272 and 8282, respectively. Processor 8270 alsoincludes as part of its bus controller units point-to-point (P-P)interfaces 8276 and 8278; similarly, second processor 8280 includes P-Pinterfaces 8286 and 8288. Processors 8270, 8280 may exchange informationvia a point-to-point (P-P) interface 8250 using P-P interface circuits8278, 8288. As shown in FIG. 82, IMCs 8272 and 8282 couple theprocessors to respective memories, namely a memory 8232 and a memory8234, which may be portions of main memory locally attached to therespective processors.

Processors 8270, 8280 may each exchange information with a chipset 8290via individual P-P interfaces 8252, 8254 using point to point interfacecircuits 8276, 8294, 8286, 8298. Chipset 8290 may optionally exchangeinformation with the coprocessor 8238 via a high-performance interface8239. In one embodiment, the coprocessor 8238 is a special-purposeprocessor, such as, for example, a high-throughput MIC processor, anetwork or communication processor, compression engine, graphicsprocessor, GPGPU, embedded processor, or the like.

A shared cache (not shown) may be included in either processor oroutside of both processors, yet connected with the processors via P-Pinterconnect, such that either or both processors' local cacheinformation may be stored in the shared cache if a processor is placedinto a low power mode.

Chipset 8290 may be coupled to a first bus 8216 via an interface 8296.In one embodiment, first bus 8216 may be a Peripheral ComponentInterconnect (PCI) bus, or a bus such as a PCI Express bus or anotherthird generation I/O interconnect bus, although the scope of the presentdisclosure is not so limited.

As shown in FIG. 82, various I/O devices 8214 may be coupled to firstbus 8216, along with a bus bridge 8218 which couples first bus 8216 to asecond bus 8220. In one embodiment, one or more additional processor(s)8215, such as coprocessors, high-throughput MIC processors, GPGPU's,accelerators (such as, e.g., graphics accelerators or digital signalprocessing (DSP) units), field programmable gate arrays, or any otherprocessor, are coupled to first bus 8216. In one embodiment, second bus8220 may be a low pin count (LPC) bus. Various devices may be coupled toa second bus 8220 including, for example, a keyboard and/or mouse 8222,communication devices 8227 and a storage unit 8228 such as a disk driveor other mass storage device which may include instructions/code anddata 8230, in one embodiment. Further, an audio I/O 8224 may be coupledto the second bus 8220. Note that other architectures are possible. Forexample, instead of the point-to-point architecture of FIG. 82, a systemmay implement a multi-drop bus or other such architecture.

Referring now to FIG. 83, shown is a block diagram of a second morespecific exemplary system 8300 in accordance with an embodiment of thepresent disclosure Like elements in FIGS. 82 and 83 bear like referencenumerals, and certain aspects of FIG. 82 have been omitted from FIG. 83in order to avoid obscuring other aspects of FIG. 83.

FIG. 83 illustrates that the processors 8270, 8280 may includeintegrated memory and I/O control logic (“CL”) 8272 and 8282,respectively. Thus, the CL 8272, 8282 include integrated memorycontroller units and include I/O control logic. FIG. 83 illustrates thatnot only are the memories 8232, 8234 coupled to the CL 8272, 8282, butalso that I/O devices 8314 are also coupled to the control logic 8272,8282. Legacy I/O devices 8315 are coupled to the chipset 8290.

Referring now to FIG. 84, shown is a block diagram of a SoC 8400 inaccordance with an embodiment of the present disclosure. Similarelements in FIG. 80 bear like reference numerals. Also, dashed linedboxes are optional features on more advanced SoCs. In FIG. 84, aninterconnect unit(s) 8402 is coupled to: an application processor 8410which includes a set of one or more cores 202A-N and shared cacheunit(s) 8006; a system agent unit 8010; a bus controller unit(s) 8016;an integrated memory controller unit(s) 8014; a set or one or morecoprocessors 8420 which may include integrated graphics logic, an imageprocessor, an audio processor, and a video processor; an static randomaccess memory (SRAM) unit 8430; a direct memory access (DMA) unit 8432;and a display unit 8440 for coupling to one or more external displays.In one embodiment, the coprocessor(s) 8420 include a special-purposeprocessor, such as, for example, a network or communication processor,compression engine, GPGPU, a high-throughput MIC processor, embeddedprocessor, or the like.

Embodiments (e.g., of the mechanisms) disclosed herein may beimplemented in hardware, software, firmware, or a combination of suchimplementation approaches. Embodiments of the disclosure may beimplemented as computer programs or program code executing onprogrammable systems comprising at least one processor, a storage system(including volatile and non-volatile memory and/or storage elements), atleast one input device, and at least one output device.

Program code, such as code 8230 illustrated in FIG. 82, may be appliedto input instructions to perform the functions described herein andgenerate output information. The output information may be applied toone or more output devices, in known fashion. For purposes of thisapplication, a processing system includes any system that has aprocessor, such as, for example; a digital signal processor (DSP), amicrocontroller, an application specific integrated circuit (ASIC), or amicroprocessor.

The program code may be implemented in a high level procedural or objectoriented programming language to communicate with a processing system.The program code may also be implemented in assembly or machinelanguage, if desired. In fact, the mechanisms described herein are notlimited in scope to any particular programming language. In any case,the language may be a compiled or interpreted language.

One or more aspects of at least one embodiment may be implemented byrepresentative instructions stored on a machine-readable medium whichrepresents various logic within the processor, which when read by amachine causes the machine to fabricate logic to perform the techniquesdescribed herein. Such representations, known as “IP cores” may bestored on a tangible, machine readable medium and supplied to variouscustomers or manufacturing facilities to load into the fabricationmachines that actually make the logic or processor.

Such machine-readable storage media may include, without limitation,non-transitory, tangible arrangements of articles manufactured or formedby a machine or device, including storage media such as hard disks, anyother type of disk including floppy disks, optical disks, compact diskread-only memories (CD-ROMs), compact disk rewritable's (CD-RWs), andmagneto-optical disks, semiconductor devices such as read-only memories(ROMs), random access memories (RAMs) such as dynamic random accessmemories (DRAMs), static random access memories (SRAMs), erasableprogrammable read-only memories (EPROMs), flash memories, electricallyerasable programmable read-only memories (EEPROMs), phase change memory(PCM), magnetic or optical cards, or any other type of media suitablefor storing electronic instructions.

Accordingly, embodiments of the disclosure also include non-transitory,tangible machine-readable media containing instructions or containingdesign data, such as Hardware Description Language (HDL), which definesstructures, circuits, apparatuses, processors and/or system featuresdescribed herein. Such embodiments may also be referred to as programproducts.

Emulation (Including Binary Translation, Code Morphing, Etc.)

In some cases, an instruction converter may be used to convert aninstruction from a source instruction set to a target instruction set.For example, the instruction converter may translate (e.g., using staticbinary translation, dynamic binary translation including dynamiccompilation), morph, emulate, or otherwise convert an instruction to oneor more other instructions to be processed by the core. The instructionconverter may be implemented in software, hardware, firmware, or acombination thereof. The instruction converter may be on processor, offprocessor, or part on and part off processor.

FIG. 85 is a block diagram contrasting the use of a software instructionconverter to convert binary instructions in a source instruction set tobinary instructions in a target instruction set according to embodimentsof the disclosure. In the illustrated embodiment, the instructionconverter is a software instruction converter, although alternativelythe instruction converter may be implemented in software, firmware,hardware, or various combinations thereof. FIG. 85 shows a program in ahigh level language 8502 may be compiled using an x86 compiler 8504 togenerate x86 binary code 8506 that may be natively executed by aprocessor with at least one x86 instruction set core 8516. The processorwith at least one x86 instruction set core 8516 represents any processorthat can perform substantially the same functions as an Intel processorwith at least one x86 instruction set core by compatibly executing orotherwise processing (1) a substantial portion of the instruction set ofthe Intel x86 instruction set core or (2) object code versions ofapplications or other software targeted to run on an Intel processorwith at least one x86 instruction set core, in order to achievesubstantially the same result as an Intel processor with at least onex86 instruction set core. The x86 compiler 8504 represents a compilerthat is operable to generate x86 binary code 8506 (e.g., object code)that can, with or without additional linkage processing, be executed onthe processor with at least one x86 instruction set core 8516.Similarly, FIG. 85 shows the program in the high level language 8502 maybe compiled using an alternative instruction set compiler 8508 togenerate alternative instruction set binary code 8510 that may benatively executed by a processor without at least one x86 instructionset core 8514 (e.g., a processor with cores that execute the MIPSinstruction set of MIPS Technologies of Sunnyvale, Calif. and/or thatexecute the ARM instruction set of ARM Holdings of Sunnyvale, Calif.).The instruction converter 8512 is used to convert the x86 binary code8506 into code that may be natively executed by the processor without anx86 instruction set core 8514. This converted code is not likely to bethe same as the alternative instruction set binary code 8510 because aninstruction converter capable of this is difficult to make; however, theconverted code will accomplish the general operation and be made up ofinstructions from the alternative instruction set. Thus, the instructionconverter 8512 represents software, firmware, hardware, or a combinationthereof that, through emulation, simulation or any other process, allowsa processor or other electronic device that does not have an x86instruction set processor or core to execute the x86 binary code 8506.

1. An apparatus comprising: a spatial array of processing elements toreceive an input of a dataflow graph comprising a plurality of nodes,wherein the dataflow graph is to be overlaid into the spatial array ofprocessing elements with each node represented as a dataflow operator inthe spatial array of processing elements, and the spatial array ofprocessing elements is to perform an operation by a respective, incomingoperand set arriving at each of the dataflow operators; a plurality ofrequest address file circuits coupled to the spatial array of processingelements and a cache memory, each request address file circuit of theplurality of request address file circuits to access data in the cachememory in response to a request for data access from the spatial arrayof processing elements; a plurality of translation lookaside bufferscomprising a translation lookaside buffer in each of the plurality ofrequest address file circuits to provide an output of a physical addressfor an input of a virtual address; and a translation lookaside buffermanager circuit comprising a higher-level translation lookaside bufferthan the plurality of translation lookaside buffers, the translationlookaside buffer manager circuit to perform a first page walk in thecache memory for a miss of an input of a virtual address into a firsttranslation lookaside buffer and into the higher-level translationlookaside buffer to determine a physical address mapped to the virtualaddress, and store a mapping of the virtual address to the physicaladdress from the first page walk in the higher-level translationlookaside buffer to cause the higher-level translation lookaside bufferto send the physical address to the first translation lookaside bufferin a first request address file circuit.
 2. The apparatus of claim 1,wherein the translation lookaside buffer manager circuit is to:concurrently, with the first page walk, perform a second page walk inthe cache memory, wherein the second page walk is for a miss of an inputof a virtual address into a second translation lookaside buffer and intothe higher-level translation lookaside buffer to determine a physicaladdress mapped to the virtual address, and store a mapping of thevirtual address to the physical address from the second page walk in thehigher-level translation lookaside buffer to cause the higher-leveltranslation lookaside buffer to send the physical address to the secondtranslation lookaside buffer in a second request address file circuit.3. The apparatus of claim 1, wherein receipt of the physical address inthe first translation lookaside buffer is to cause the first requestaddress file circuit to perform a data access for the request for dataaccess from the spatial array of processing elements on the physicaladdress in the cache memory.
 4. The apparatus of claim 1, wherein thetranslation lookaside buffer manager circuit is to insert an indicatorin the higher-level translation lookaside buffer for the miss of theinput of the virtual address in the first translation lookaside bufferand the higher-level translation lookaside buffer to prevent anadditional page walk for the input of the virtual address during thefirst page walk.
 5. The apparatus of claim 1, wherein the translationlookaside buffer manager circuit is to receive a shootdown message froma requesting entity for a mapping of a physical address to a virtualaddress, invalidate the mapping in the higher-level translationlookaside buffer, and send shootdown messages to only those of theplurality of request address file circuits that include a copy of themapping in a respective translation lookaside buffer, wherein each ofthose of the plurality of request address file circuits are to send anacknowledgement message to the translation lookaside buffer managercircuit, and the translation lookaside buffer manager circuit is to senda shootdown completion acknowledgment message to the requesting entitywhen all acknowledgement messages are received.
 6. The apparatus ofclaim 1, wherein the translation lookaside buffer manager circuit is toreceive a shootdown message from a requesting entity for a mapping of aphysical address to a virtual address, invalidate the mapping in thehigher-level translation lookaside buffer, and send shootdown messagesto all of the plurality of request address file circuits, wherein eachof the plurality of request address file circuits are to send anacknowledgement message to the translation lookaside buffer managercircuit, and the translation lookaside buffer manager circuit is to senda shootdown completion acknowledgment message to the requesting entitywhen all acknowledgement messages are received.
 7. A method comprising:overlaying an input of a dataflow graph comprising a plurality of nodesinto a spatial array of processing elements with each node representedas a dataflow operator in the spatial array of processing elements;coupling a plurality of request address file circuits to the spatialarray of processing elements and a cache memory with each requestaddress file circuit of the plurality of request address file circuitsaccessing data in the cache memory in response to a request for dataaccess from the spatial array of processing elements; providing anoutput of a physical address for an input of a virtual address into atranslation lookaside buffer of a plurality of translation lookasidebuffers comprising a translation lookaside buffer in each of theplurality of request address file circuits; coupling a translationlookaside buffer manager circuit comprising a higher-level translationlookaside buffer than the plurality of translation lookaside buffers tothe plurality of request address file circuits and the cache memory; andperforming a first page walk in the cache memory for a miss of an inputof a virtual address into a first translation lookaside buffer and intothe higher-level translation lookaside buffer with the translationlookaside buffer manager circuit to determine a physical address mappedto the virtual address, and store a mapping of the virtual address tothe physical address from the first page walk in the higher-leveltranslation lookaside buffer to cause the higher-level translationlookaside buffer to send the physical address to the first translationlookaside buffer in a first request address file circuit.
 8. The methodof claim 7, further comprising: concurrently, with the first page walk,performing a second page walk in the cache memory with the translationlookaside buffer manager circuit, wherein the second page walk is for amiss of an input of a virtual address into a second translationlookaside buffer and into the higher-level translation lookaside bufferto determine a physical address mapped to the virtual address, andstoring a mapping of the virtual address to the physical address fromthe second page walk in the higher-level translation lookaside buffer tocause the higher-level translation lookaside buffer to send the physicaladdress to the second translation lookaside buffer in a second requestaddress file circuit.
 9. The method of claim 7, further comprisingcausing the first request address file circuit to perform a data accessfor the request for data access from the spatial array of processingelements on the physical address in the cache memory in response toreceipt of the physical address in the first translation lookasidebuffer.
 10. The method of claim 7, further comprising inserting, withthe translation lookaside buffer manager circuit, an indicator in thehigher-level translation lookaside buffer for the miss of the input ofthe virtual address in the first translation lookaside buffer and thehigher-level translation lookaside buffer to prevent an additional pagewalk for the input of the virtual address during the first page walk.11. The method of claim 7, further comprising receiving, with thetranslation lookaside buffer manager circuit, a shootdown message from arequesting entity for a mapping of a physical address to a virtualaddress, invalidating the mapping in the higher-level translationlookaside buffer, and sending shootdown messages to only those of theplurality of request address file circuits that include a copy of themapping in a respective translation lookaside buffer, wherein each ofthose of the plurality of request address file circuits are to send anacknowledgement message to the translation lookaside buffer managercircuit, and the translation lookaside buffer manager circuit is to senda shootdown completion acknowledgment message to the requesting entitywhen all acknowledgement messages are received.
 12. The method of claim7, further comprising receiving, with the translation lookaside buffermanager circuit, a shootdown message from a requesting entity for amapping of a physical address to a virtual address, invalidate themapping in the higher-level translation lookaside buffer, and sendingshootdown messages to all of the plurality of request address filecircuits, wherein each of the plurality of request address file circuitsare to send an acknowledgement message to the translation lookasidebuffer manager circuit, and the translation lookaside buffer managercircuit is to send a shootdown completion acknowledgment message to therequesting entity when all acknowledgement messages are received.
 13. Anapparatus comprising: a spatial array of processing elements to receivean input of a dataflow graph comprising a plurality of nodes, whereinthe dataflow graph is to be overlaid into the spatial array ofprocessing elements with each node represented as a dataflow operator inthe spatial array of processing elements, and the spatial array ofprocessing elements is to perform an operation by a respective, incomingoperand set arriving at each of the dataflow operators; a plurality ofrequest address file circuits coupled to the spatial array of processingelements and a plurality of cache memory banks, each request addressfile circuit of the plurality of request address file circuits to accessdata in the plurality of cache memory banks in response to a request fordata access from the spatial array of processing elements; a pluralityof translation lookaside buffers comprising a translation lookasidebuffer in each of the plurality of request address file circuits toprovide an output of a physical address for an input of a virtualaddress; a plurality of higher-level, than the plurality of translationlookaside buffers, translation lookaside buffers comprising ahigher-level translation lookaside buffer in each of the plurality ofcache memory banks to provide an output of a physical address for aninput of a virtual address; and a translation lookaside buffer managercircuit to perform a first page walk in the plurality of cache memorybanks for a miss of an input of a virtual address into a firsttranslation lookaside buffer and into a first higher-level translationlookaside buffer to determine a physical address mapped to the virtualaddress, and store a mapping of the virtual address to the physicaladdress from the first page walk in the first higher-level translationlookaside buffer to cause the first higher-level translation lookasidebuffer to send the physical address to the first translation lookasidebuffer in a first request address file circuit.
 14. The apparatus ofclaim 13, wherein the translation lookaside buffer manager circuit isto: concurrently, with the first page walk, perform a second page walkin the plurality of cache memory banks, wherein the second page walk isfor a miss of an input of a virtual address into a second translationlookaside buffer and into a second higher-level translation lookasidebuffer to determine a physical address mapped to the virtual address,and store a mapping of the virtual address to the physical address fromthe second page walk in the second higher-level translation lookasidebuffer to cause the second higher-level translation lookaside buffer tosend the physical address to the second translation lookaside buffer ina second request address file circuit.
 15. The apparatus of claim 13,wherein receipt of the physical address in the first translationlookaside buffer is to cause the first request address file circuit toperform a data access for the request for data access from the spatialarray of processing elements on the physical address in the plurality ofcache memory banks.
 16. The apparatus of claim 13, wherein thetranslation lookaside buffer manager circuit is to insert an indicatorin the first higher-level translation lookaside buffer for the miss ofthe input of the virtual address in the first translation lookasidebuffer and the first higher-level translation lookaside buffer toprevent an additional page walk for the input of the virtual addressduring the first page walk.
 17. The apparatus of claim 13, wherein thetranslation lookaside buffer manager circuit is to receive a shootdownmessage from a requesting entity for a mapping of a physical address toa virtual address, invalidate the mapping in a higher-level translationlookaside buffer storing the mapping, and send shootdown messages toonly those of the plurality of request address file circuits thatinclude a copy of the mapping in a respective translation lookasidebuffer, wherein each of those of the plurality of request address filecircuits are to send an acknowledgement message to the translationlookaside buffer manager circuit, and the translation lookaside buffermanager circuit is to send a shootdown completion acknowledgment messageto the requesting entity when all acknowledgement messages are received.18. The apparatus of claim 13, wherein the translation lookaside buffermanager circuit is to receive a shootdown message from a requestingentity for a mapping of a physical address to a virtual address,invalidate the mapping in a higher-level translation lookaside bufferstoring the mapping, and send shootdown messages to all of the pluralityof request address file circuits, wherein each of the plurality ofrequest address file circuits are to send an acknowledgement message tothe translation lookaside buffer manager circuit, and the translationlookaside buffer manager circuit is to send a shootdown completionacknowledgment message to the requesting entity when all acknowledgementmessages are received.
 19. A method comprising: overlaying an input of adataflow graph comprising a plurality of nodes into a spatial array ofprocessing elements with each node represented as a dataflow operator inthe spatial array of processing elements; coupling a plurality ofrequest address file circuits to the spatial array of processingelements and a plurality of cache memory banks with each request addressfile circuit of the plurality of request address file circuits accessingdata in the plurality of cache memory banks in response to a request fordata access from the spatial array of processing elements; providing anoutput of a physical address for an input of a virtual address into atranslation lookaside buffer of a plurality of translation lookasidebuffers comprising a translation lookaside buffer in each of theplurality of request address file circuits; providing an output of aphysical address for an input of a virtual address into a higher-level,than the plurality of translation lookaside buffers, translationlookaside buffer of a plurality of higher-level translation lookasidebuffers comprising a higher-level translation lookaside buffer in eachof the plurality of cache memory banks; coupling a translation lookasidebuffer manager circuit to the plurality of request address file circuitsand the plurality of cache memory banks; and performing a first pagewalk in the plurality of cache memory banks for a miss of an input of avirtual address into a first translation lookaside buffer and into afirst higher-level translation lookaside buffer with the translationlookaside buffer manager circuit to determine a physical address mappedto the virtual address, and store a mapping of the virtual address tothe physical address from the first page walk in the first higher-leveltranslation lookaside buffer to cause the first higher-level translationlookaside buffer to send the physical address to the first translationlookaside buffer in a first request address file circuit.
 20. The methodof claim 19, further comprising: concurrently, with the first page walk,performing a second page walk in the plurality of cache memory bankswith the translation lookaside buffer manager circuit, wherein thesecond page walk is for a miss of an input of a virtual address into asecond translation lookaside buffer and into a second higher-leveltranslation lookaside buffer to determine a physical address mapped tothe virtual address, and storing a mapping of the virtual address to thephysical address from the second page walk in the second higher-leveltranslation lookaside buffer to cause the second higher-leveltranslation lookaside buffer to send the physical address to the secondtranslation lookaside buffer in a second request address file circuit.21. The method of claim 19, further comprising causing the first requestaddress file circuit to perform a data access for the request for dataaccess from the spatial array of processing elements on the physicaladdress in the plurality of cache memory banks in response to receipt ofthe physical address in the first translation lookaside buffer.
 22. Themethod of claim 19, further comprising inserting, with the translationlookaside buffer manager circuit, an indicator in the first higher-leveltranslation lookaside buffer for the miss of the input of the virtualaddress in the first translation lookaside buffer and the firsthigher-level translation lookaside buffer to prevent an additional pagewalk for the input of the virtual address during the first page walk.23. The method of claim 19, further comprising receiving, with thetranslation lookaside buffer manager circuit, a shootdown message from arequesting entity for a mapping of a physical address to a virtualaddress, invalidating the mapping in a higher-level translationlookaside buffer storing the mapping, and sending shootdown messages toonly those of the plurality of request address file circuits thatinclude a copy of the mapping in a respective translation lookasidebuffer, wherein each of those of the plurality of request address filecircuits are to send an acknowledgement message to the translationlookaside buffer manager circuit, and the translation lookaside buffermanager circuit is to send a shootdown completion acknowledgment messageto the requesting entity when all acknowledgement messages are received.24. The method of claim 19, further comprising receiving, with thetranslation lookaside buffer manager circuit, a shootdown message from arequesting entity for a mapping of a physical address to a virtualaddress, invalidate the mapping in a higher-level translation lookasidebuffer storing the mapping, and sending shootdown messages to all of theplurality of request address file circuits, wherein each of theplurality of request address file circuits are to send anacknowledgement message to the translation lookaside buffer managercircuit, and the translation lookaside buffer manager circuit is to senda shootdown completion acknowledgment message to the requesting entitywhen all acknowledgement messages are received.